When objects are stored wholesale in an object store, I call it an
object database. When object data is stored in a SQL database and then
managed by some intermediary API, I call it a persistence layer.
So, perhaps we're splitting hairs here.
Roy Gaber wrote:
the ideal high-performance database for Java applications. Caché data
can be accessed with SQL via JDBC, and Caché classes can be projected as
(snip)
Caché’s efficient multidimensional data engine has excellent SQL
response – up to 20 times faster than relational databases. Caché
The key here is that Cache is obviously storing their data in a SQL data
base. A lot of object *data* is persisted in SQL databases, but the
Cache objects themselves aren't?
So, I would call Cache Objects a persistence layer, but not a true
object store.
Compare with Java Data Objects:
"JDO defines interfaces and classes to be used by application
programmers when using classes whose instances are to be stored in
persistent storage (persistence-capable classes)."
JDO can use b-tree storages to store Java object trees directly.
*That's* an object store.
Richard
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
