I agree with David. I can't imagine any reason why one would trade in the relational model for an OO
one. If OFBiz's performance is an issue, then maybe you should invest in a better database or faster
hardware.
-Adrian
David E Jones wrote:
Actually no, the Entity Engine never does object-relational mapping.
There is never a mapping to an object form for data structures in OFBiz.
The is the whole point of how the entity engine, service engine, form
widget and other related elements are designed.
OR mapping is a waste of time, so we use relational data structures top
to bottom and have tools to make that easier.
-David
David Shere wrote:
The ad I'm looking at says:
"To store Java objects, relational and object-relational databases
must translate them into another format. This object-relational
mapping (ORM) is a drag on performance and boosts storage demands.
"McObject's Perst, as an all-Java, object-oriented database, stores
Java objects as Java objects, for greater efficiency and performance,
and a smaller footprint."
http://www.mcobject.com/perst
Is the relational data model you're talking about not the same as the
object-relational database this ad is talking about?
David E Jones wrote:
If it persists Java objects then it is an object database and not a
relational one. OFBiz is built on a relational data model and
relational database. These two are VERY different so no, you couldn't
use it with OFBiz unless it has a relational layer (with JDBC driver)
built on the object database.
For anyone curious this is an interesting little bit of computer
science to read about, but I don't know of any good, accessible
resources on the net (just old textbooks for me...).
-David
Adrian Crum wrote:
OFBiz attempts to be database agnostic. Database vendor specific
features are avoided.
-Adrian
David Shere wrote:
I've read about this Perst database that stores Java objects as
Java objects. Has there been any talk about Ofbiz using this?
