4 ms·
These are great examples towards the fact that the relational model isn't always the best way to go. Especially with regards to an evolving model. In object or
by voidpointer 18y ago
These are great examples towards the fact that the relational model isn't always the best way to go. Especially with regards to an evolving model.
In object oriented models, polymorphism can be employed to extend an existing model with rather minimal impact. Introducing, for instance, a subtype for an address in a relational model isn't easily done.
I'd rather model in OO land and use the DB as dumb object store.
I haven't implemented a serious project based on an real OO database. Any experiences you guys would want to share with regards to model flexibility with an OODB?
- litewulf 18y agoSingle table inheritance?
- seiji 18y agopeople from the wild mysql badlands may not understand your point. here you go: http://www.postgresql.org/docs/current/static/ddl-inherit.html http://www.postgresql.org/docs/current/static/ddl-inherit.ht...
- litewulf 18y agoI actually use MySQL ;) Its pretty web two point oh-y. Honestly, when I say something like "single table inheritance" I wish people would use say a search engine and type it in and see what comes out. Its a pretty unique phrase that gets you what you want... don't enable people who expect everything to be explained to them! (Not uninformed-ist mind you.)
- bhiggins 18y agoRM does not address inheritance but it doesn't preclude it. see the third manifesto.