用于移植对象数据库的资源和指南数据到关系数据库
有谁有关于对象数据库到关系数据库转换技术的信息吗？
我已经完成了标准搜索，只得出 从面向对象数据库到关系数据库的数据转换到目前为止。这是一篇很好的论文，但我希望能有更多......
Does anyone have any pointers to information on techniques for object database to relational database conversion?
I've done the standard searches and have only come up with Data Conversion from Object-Oriented to Relational database so far. It's a good paper, but I was hoping for more....
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我应该在某个地方有这个，让我看看，它应该在靠近那篇论文的地方 Upgrading from c# to cobol :)
基本上所有关于 ORM 技术的文档（如 Hibernate、Toplink）都可以帮助你。您可能会遇到获得良好性能、处理行为和对象版本的问题。
[编辑]
ac 程序的对象数据库？或者持久化引擎（如 ctree？）
[编辑2]
那么它不是一个对象数据库，而是一个持久性引擎，没有对象版本，存储行为？那么一般的风格可以是网络或分层数据库。你们有什么API？可以拦截电话吗？
I should have that here somewhere, let me look, it should be somewhere close to that paper Upgrading from c# to cobol :)
Basically all documentation on ORM technology (like Hibernate, Toplink) can help you. You'll probably run into issues getting good performance, handling behaviour, and object versions.
[edit]
An object database for a c program? Or a persistence engine (like ctree?)
[edit2]
So it's not an object database but a persistence engine, no object versions, storing of behaviour? Then the general style could be of a network or hierarchical database. What API do you have? Can you intercept calls?
您从哪个 ODBMS 进行转换？如果这只是可扩展性或功能的问题，您应该考虑转向商业 ODBMS 或 db4objects。如果应用程序因为 RDBMS 性能不佳而使用 ODBMS，那么重新使用 ODBMS 可能不是一个好主意。如果由于其他原因您必须迁移到 RDBMS，我会考虑 Hibernate，但这会带来性能损失，而且您必须永远维护映射层。
Which ODBMS are you converting from? If it's simply a matter of scalability or functionality you should consider moving to a commercial ODBMS or db4objects. If the application uses an ODBMS because an RDBMS wasn't performing well then moving back to one probably isn't a good idea. If you have to move to an RDBMS for another reason I'd look at Hibernate, but there will be a performance penalty and you'll have to maintain the mapping layer forever.