I'm curious what approach people use for persisting objects in the db. Let's say I have a Person object. Is it better to have that Person object contain all of the Business methods to work on the object as well as the methods to persist itself or is it better to set up a separate PersonDAO object that deals with all of the database interactions and keep all database interaction out of the Person object?

Along those lines, I'm also curious how people actually do their updates. Do you first update all of the properties of an object and then call a Persisit() method or when a setter method is called do you have it update the object property and then update that property in the db? Seems like a lot of extra db traffic to do it the second way but it would cut down on some persistance logic.

I'm still a little new at working with CFCs in a more OO way so any help would be greatly appreciated.

Stephen
----------------------------------------------------------
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 www.mail-archive.com/[EMAIL PROTECTED]

Reply via email to