有关如何编写工具以将数据库数据从支持 Hibernate 的 Java 应用程序的一个版本迁移到下一个版本的书籍/文章/建议
我们开发并支持使用 Hibernate 作为对象关系映射工具来将 Java 对象保存到数据库中的应用程序。不幸的是，OurApp 1.0 和 OurApp 2.0 之间的对象模型以及数据库模式发生了一些变化。因此，我们希望编写一个自动化工具，将数据从使用 OurApp 1.0 的客户数据库迁移到模式与 OurApp 2.0 匹配的新数据库。
我们正在考虑创建一个工具，每个 Java 类都有两个版本。例如，我们可能有一个 Java 类 MyObject_1_0 与 OurApp 1.0 中出现的 MyObject 类匹配，还有一个与 OurApp 2.0 中出现的 MyObject 类匹配的 MyObject_2_0。然后，我们将编写知道如何将 MyObject_1_0 转换为 MyObject_2_0 的代码。
然而，这不是我以前做过的事情，我想知道这是否是最好的方法。如果我能回顾一些关于最佳实践和常见陷阱的文献和研究，那就太好了。在我们研究最有效的方法时，有人可以推荐我可能觉得有用的书籍或文章吗？
谢谢！
We develop and support and application that uses Hibernate as an Object-Relational Mapping tool to persist our Java objects into the database. Unfortunately, there have been some changes in object model, and thus the database schema, between OurApp 1.0 and OurApp 2.0. So, we would like to write an automated tool to migrate the data from databases of customers using OurApp 1.0 to a new database with a schema matching OurApp 2.0.
We were thinking of creating a tool that has two versions of each Java class. For example we might have a Java class MyObject_1_0 that matches the MyObject class as it appears in OurApp 1.0 and a MyObject_2_0 that matches the MyObject class as it appears in OurApp 2.0. We would then write code that knows how to convert a MyObject_1_0 to a MyObject_2_0.
However, this isn't something I've done before and I'd like to know if this is the best approach. It would be nice if I could review some literature and research on best practices and common pitfalls. Can anyone recommend books or articles that I might find useful as we research the most effective ways to do this?
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
正如 Peter 所建议的，我确实会考虑使用数据库迁移工具，这应该会更加高效，并且最终的工作也会更少，正如我们将看到的。由于目标数据库不在您的控制之下，我会寻找一种允许以与数据库无关的方式描述更改的东西，例如 liquibase，它使用 XML。
支持liquibase的另一个论点是它提供了Hibernate 集成，这是您场景的杀手级功能：它可以通过将实体（XML 或注释）的新映射与 <旧数据库。即使结果需要一些调整，这也会大大简化工作。从文档中：
您可以为所有受支持的数据库提供 SQL 脚本，或者简单地将工具包装在某些 Ant 构建中。
这也是在您的开发过程中采用此类工具的机会。
As suggested by Peter, I would indeed consider using a database migrations tool instead, this should be much more efficient and also less work at the end as we'll see. And since the target database isn't under your control, I would look for a something allowing to describe changes in a database agnostic way, like liquibase, which uses XML.
Another argument in favor of liquibase is that it provides Hibernate integration which is a killer feature for your scenario: it can generate a migration script by comparing the new mappings of your entities (XML or annotations) against an old database. Even if the result needs some tweaking, this should highly simplify the work. From the documentation:
And you could either provide SQL script for all supported database or simply wrap the tool in some Ant build.
This is also an opportunity to adopt such a tool in your development process.
我首先建议查看 dbMigrate 和 liquiBase 或许还有 dbMaintain。
这些库、工具是专门为进行架构迁移而构建的。他们使用不同的方法。
它们可能是您解决方案的一部分，甚至本身就足够了。
I would first recommend to look at dbMigrate and liquiBase and maybe also dbMaintain.
These libraries, tools are purpose build to do schema migrations. They use different approaches.
They may be part of your solution, or even be sufficient in themselves.