Here's a question: If you write your application's code in an OO language -
such as C#, VB.NET, or managed C++ - why not write database query and update
code in the same language? It would certainly make life simpler, wouldn't it?
At the very least, you'd only have to hold one language in your head - not
your programming language and SQL.
That's the very least of the advantages you'd gain by choosing an OO database
instead of an RDBMS. The metaphor "impedance mismatch" has frequently been
used to illustrate the problems that arise from using a relational database
as the back end to an OO application. Admittedly, it's a somewhat overused
metaphor, but it still serves its purpose. It illustrates the fact that
relationships among objects - referencing, containment, polymorp... (more)
When your next Java application calls for a database backend, before you
reach for JDBC and a relational database, stop for a moment and consider
another possibility: an object database.
As we hope to show in this article, an object database may not only simplify
coding chores, but its capabilities may enable application solutions that you
would otherwise not thought of.
Of course, the m... (more)
When your next application calls for a database backend, stop for a moment
and consider another possibility: an object database.
As we hope to show in this article, an object database may not only simplify
coding chores, but its capabilities may enable application solutions that you
would otherwise not thought of.
Of course, the most apparent benefit you'll get from using an object databas... (more)