可以 ORM +关系数据库算不算对象关系数据库管理系统？
我想知道为什么 ORM 如此流行，每个人都在使用 JDO 和 JDA 规范的 ORM 实现，而不是使用也实现这些规范的对象数据库。使用对象数据库的性能要好得多。
如果我说这是因为开发人员需要同时使用对象模型和关系模型，我对吗？在他们的应用程序中？
ORDBM 怎么样？是否有任何 ORDBM （值得一试）或者可以将对象关系映射与关系数据库一起视为 ORDBM 吗？
I'm wondering why is ORM so popular and everybody is using ORM implementations of JDO and JDA specifications, instead of using object databases that implements these specifications as well. The performance is much better using Object database.
Am I right if I say that it is because developers need to use both object model and relational model in their applications ?
What about ORDBMs ? Is there any ORDBM (which worths a try) around or can Object Relational Mapping together with relational database be considered ORDBM ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
人们使用带有 OR Mapper 的 RDBMS 而不是对象数据库的主要原因是 RDBMS 根深蒂固，得到了每个人的充分理解和支持。如果您使用对象数据库，您将很难
可能仍然存在很多疑问（无论合理与否，我不能比如说）对象数据库是否真的可以在真实场景中提供相同或更好的性能和安全性。
The main reason why people use an RDBMS with an OR Mapper rather than an object database is that RDBMS are deeply entrenched, well understood and well supported by everyone. If you use an object database you'll have problems
There's probably also still a lot of doubts (whether justified or not I can't say) whether object databases can really deliver the same or better performance and safety in a real word scenario.
根据我的经验，使用对象数据库可以减少更多的代码，并且使项目更加简洁。
它使 RDBMS + ORM（LINQ 到实体）的 6 周学习曲线与对象数据库（对于 db4o）的 1 周学习曲线有所不同。
In my experience, using an object database resulted in much less code, and a much cleaner project.
It made the difference between a 6-week learning curve for an RDBMS + ORM (LINQ-to-Entities) and a 1-week learning curve for object databases (for db4o).
您可能熟悉的常用 DBMS（例如 Oracle、SQL Server、DB2、MySQL、PostGreSQL）都不是关系型的。它们基于 SQL 模型，尽管它在某些方面类似于关系模型，但还是有很大不同。
对象关系型 DBMS 与关系型 DBMS 含义相同。换句话说，RDBMS 原则上将支持任何无限的数据类型集以及对它们的关系操作。 O/R 映射软件实际上只是解决了 SQL DBMS 不能很好地做到这一点的事实。
The commonly used DBMSs you may be familiar with (e.g. Oracle, SQL Server, DB2, MySQL, PostGreSQL) are not relational. They are based on the SQL model, which is something quite different even though it resembles the relational model in some ways.
An Object-Relational DBMS means the same thing as a Relational DBMS. It's another way of saying that a RDBMS in principle will support any unlimited set of data types and relational operations upon them. O/R Mapping software really only addresses the fact that SQL DBMSs don't do that very well.