{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 Evening l夕情丶 的问题《Are Object oriented databases still in use?》','https://www.manongdao.com/q-1231316.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Quite a while ago, I heard about Object databases. Cool concept and all. Now, with the event of ORMs everywhere, does anyone still use any of the Object oriented Databases systems? Are they relevant? Are they practical?
相关问题
- how to define constructor for Python's new Nam
- Keeping track of variable instances
- Object.create() bug?
- NOT DISTINCT query in mySQL
- Flush single app django 1.9
相关文章
- 接口B继承接口A，但是又不添加新的方法。这样有什么意义吗？
- Connection pooling vs persist connection mysqli
- NameError: name 'self' is not defined, eve
- Implementation Strategies for Object Orientation
- Check if the Type of an Object is inherited from a
- When to use Interfaces in PHP
- Are default parameters bad practice in OOP?
- Speed up sqlFetch()
Using GemStone for a large business application. It's great and It's very practical. We've used it for several years and over that time it has enabled us to do a lot with very little resources. Unfortunately there are and have been numerous misconceptions about object databases and I think this makes them less relevant in the business world. Hopefully something like GLASS (GemStone, Linux, and Seaside Smalltalk) will change that going into the future.
Check out db4o.
In real life, that's simply not true. A major reason for our problems with databases (I saw a claim 30% of all database rows contain errors) is the use of very primitive typing and validating in SQL. In addition, even though they are named relational, they are very bad at handling relations . The result is denormalized datamodels and resulting update errors.
The reason businesses like relational databases is because they are very predictable. They have to spend a lot of money on them, they need a lot of developers and maintenance doing mostly routine jobs. They fail to see the amount of duplication that could be eliminated as an advantage. The routine work allows developers to absorb the risks of the difficult work. Switching to an OODB would keep the less predictable work.
Because the cost of their software isn't easy enough to find out.
I checked out Objectivity, db4o, versant, and none of them have the price of software up front on their website.
I've already almost lost interest just because of that.
Does anyone know anywhere where there is a pricing and license comparison of all these different oodbs?