I do it in such a way that an object may have several DAO's associated with it. If an object spans multiple tables, it will use a corresponding DAO for each table.
On Mon, 15 Nov 2004 14:22:00 -0600, Dawson, Michael <[EMAIL PROTECTED]> wrote: > But, theoretically, you shouldn't think in terms of tables, but think in > terms of objects. An object may need to store data in multiple tables. > You would then have a DAO for that object. In the DAO, you may have a > method "create()" that inserts a new record in the main table, then > inserts a default child record in a userType table. > > Or, is that the business logic that handles that? ---------------------------------------------------------- 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]
