I'm working on much the same thing at the minute and am wrapping my query as a collection and adding an extra column. I then use this extra column to store information about whether the row has been added, updated or deleted. Then when I have finished manipulating the collection. I can push all the updates back to the database. I have no idea whether this is a sensible approach but I'm running with it to see where it goes. As ever, all feedback appreciated.
Cheers, Pete (aka lad4bear)
----Original Message Follows----
From: "Toth, Cory TMC" <[EMAIL PROTECTED]>
Reply-To:
[email protected]
To: <
[email protected]>
Subject: [CFCDev] Gateway Question
Date: Sun, 1 May 2005 13:40:16 -0600
I have been reading information on the DAO / Gateways for a DB Tier of
an application. my questions is when requesting multiple rows from a
table should I be creating a collection of objects that I can iterate
through or should I just return the raw query.
Just wanted to see how other people here are handling this issue.
Cory
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/
[email protected]
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/
[email protected]
