Most object model to DBMS methodologies basically say: Design by the object and then map to DBMS as class -> table, attribute -> column, object -> row.

Object dependencies and inheritance issues are generally mapped to parent-child relationships with common keys.


>>One of my defects in moving to OOP has been in applying my knowledge of procedural coding and, I think, relational database design to OOD. I think this has seriously interfered with my grasp of n-Tier development. It's hard to separate the data from the application, IOW.
>>
>
>Mine, too. I also think many of us have that inclination as well. All part of the learning curve, lack of total understanding, adjusting to something new and emerging, and some laziness thrown in for good (bad?) measure.