I am new to PostgreSQL, mainly used MySQL before and SQLServer(for Clients Pressure; donno much), I've gone through several OODBMS Introductories over some Google Search. Most of them mainly focuses on Table <-> Object Mapping. But When using some Generic ORM Layer with any RDBMS Things are Hapily Mapped. So do we really need OODBMS ? I...
I'm planning to write an address book that stored contact information. Each contact could have an unlimited number of fields. Mostly strings and integers. But perhaps references to other Objects. What are the advantages and disadvantages of using an RDBMS with ORM vs OODBMS vs Document DBMS (like CouchDB). Thanks. ...
I've been using relational databases + object relational mappers for object persistence. I don't think this is a truly adequate solution for persistence, because it adds unnecessary overhead. It also forces me to fit objects in a table-like structure, which sometimes can't be done gracefully - it's like fitting a square in a circle - it...
I mean, with EJB, LINQ2SQL, EF etc we're trying to (at least in my perspective) map the rdb in a way so we can use the entities as objects. How come there hasn't been a surge of OODBMS since they should remove many barriers we face today, or at least lessen the burden? I'm probably overlooking something but the main reason I can see as...