yes that makes sense but then again most tables are the real world entities (objects) anyway..
I've been taught (and have tried to use) the idea that the database itself should be normalized or denormalized as appropriate to the database, not necessarily into neat little objects. Separate the persisting (DAO) layer from the persistance (DB) layer, including design and optimization.
Think of a user object, that at this time only has one address in your application. Because it only has one address and because the application doesn't do anything special with the address, you may create your user object with address inside it, rather than as a separate objects linked by composition. I would still have separate tblUser and tblUserAddress tables in a properly normalized database.
Chris
--
***********************
Chris Dempsey
Director, Information Services
UCSB Graduate Division
Abutebaris modo subjunctivo denuo
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at [EMAIL PROTECTED]
