🚀 go-pugleaf

Good Day All,

  I have found myself in the situation of trying to map C++ objects to
relational tables.  Someone I work with believes, very strongly, that
the tables and classes should be a 1 for 1 match, as this is a
normalized version of th DB Structure.

  I on the otherhand disagree.  I do not believe that the struture would
be anything close, well, at least not one for one.
His process is to go class for table, which apperntly is normalized, and
then try to tweak performance, or tune the DBMS.

  I believe that analysis of the the class structure will eventually
rear its ugly head, and by using a combination of sequence and use case
diagrams, one can determine a much more robust structure.

Any comments, suggestions, readings.

Thanks, Nick
Borland Forever ...