Community archive

Ask something
Discussion Locked

Database Design Methodologies

0 helpful
1 reply

by marcus

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Well, as it's nearing the end of the current academic term here in the UK, it's trusty old assignment time...

So, of I trudge lightly into the realm of Database design (which I'm pretty good at), when an awful question pops up on a sample paper -what's the difference between OODB design, and RDBMS? Well, I sat down, and started writing, and researching, but I thought, why not pick the brains of the finest, to see their opinions (and yes I would give them credit where it's due).

So I'll thrown it open to my peers, to get those academic, creative juices flowing, before the cloudy mirth of an alchohol filled Christmas puts IT issues to one side, at least for a few days....

1 reply

by donq

Data Modeling is Data Modeling! maybe we should call it OORDBMS for Object Oriented Relational Database Management Systems because if either part isn't modeled properly the management part goes to sleep.

The key is naming everything so EVERYONE recognizes what the stored data is AND names are UNIQUE at the "Field Level". This will "allow" many of the newer ODBC complient products to automatically write 95% of our code for us. Horray for lazy me!

This discussion is closed to new replies.