什么是“对象数据库”？什么时候使用它有益？
我非常熟悉我所理解的关系数据库，例如 mysql，其中有表、行、列和连接来确定内容之间的关系。
有人建议我在我忙于的项目中使用对象数据库，但我不知道对象数据库是什么，也不知道它何时比关系数据库更有利。
我已经用谷歌搜索过，维基百科有丰富的信息（是的，讽刺），我必须承认我遵循的几个链接并不是特别有启发性。因此我转向未来的谷歌；众包信息。有谁知道我可以阅读的好文章，或者有人可以向我解释一下。
提前致谢。
I'm quite familiar with what I understand to be relational databases such as mysql where you have tables, rows, columns and joins to figure out how content relates.
Someone suggested I use an object database for a project I'm busy with but I don't know what an object database is nor when it would be beneficial over a relational database.
I have already googled, wikipedia is a wealth of information (yes, sarcasm) and I must admit the few links I followed were not particularly enlightening. I therefore turn to the future google; crowd sourcing information. Does anyone know a good article I can read, or could anyone explain it to me.
Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
对象数据库背后的主要思想是，您将按原样存储对象在数据库中，例如，不将它们分解为关系结构，例如具有行和列的表。
基本前提是，从这样的对象数据库中检索对象会简单得多 - 只需“抓取”对象，无需映射，无需翻译或任何需要的东西。
请参阅一些链接以获取更多信息：
最大OO-DB 面临的挑战是尽可能简单地查找和检索存储的对象，并提供良好的性能。它们的缺乏广泛使用也阻碍了它们的采用。
The main idea behind an object database is that you would be storing the objects as is inside your database, e.g. not breaking them up into relational constructs like tables with rows and columns.
The basic premise is that retrieving an object from such an object database would be much simpler - just "grab" the object, no mapping, no translation or anything needed.
See some links for more information:
The biggest challenge for OO-DB is making the finding and retrieving of those objects stored as simple as possible, and also provide good performance. And their lack of widespread use also hinders their adoption.