Concept for modeling hierarchical data 2005-12-15 - By Florian Lindner
Back
Am Dienstag, 13. Dezember 2005 21:31 schrieb Dharmendra Sharan:
> Hi Florian,
>
> I haven't used Object Oriented databases as such, but have mostly come
> across Relational Databases which seem to be the mainstream approach, and
> works for most cases.
>
> In case you feel there's a strong reason that the application's usage
> profile would rely and "heavily" use the hierachical relationship, then
> you'd need to check whether it makes more sense to store your Java objects
> natively in an OO datbase as opposed to serializing them in XML and storing
> them in an XML database and work in that manner. Here are some vendor names
> for the same:
>
> a. Object Oriented data model
> - Excelon/Object Design (optimized for OO storage/rerieval)
This DB is WAY to expensive. My projekt in non-commercial/non-profit so I must
rely on freeware/OSS software. Same of Tamino.
>
> b. XML based data model
> - Tamino (optimized for XML storage/retrieval)
> - Xindice (optimized for XML storage/retrieval)
Xindice is optimized for storing a large number of smaller XML documents.
AFAIK these document itself are not organized hierarchily. Please correct if
I am wrong.
> - Excelon/Object Design
>
> c. Relational data model (optimized for Relational storage/retrieval)
> - Oracle
> - Sybase
> - SQL Server
> - MySQL (opensource!)
That will probably be the way to go (at least at the beginning.)
> - DB2
Thanks for comment,
Florian
===========================================================================
To unsubscribe, send email to listserv@(protected) and include in the body
of the message "signoff J2EE-INTEREST". For general help, send email to
listserv@(protected) and include in the body of the message "help".
|
|
