Q1. When you wrap a CFTRANSACTION around a CFQUERY, what happens technically behind the scenes? does a connection open and when everything passes without problems, does it THEN commit and close that connection (Ie </cfquery>) or is there more things happening behind the scenes that we don't know.
I ask, as its a question that i've been asked a lot of the past few months and in truth, i don't really know.
Q2. Datalocking on rows? How do most of you secure your data locking when transacting with a database, without relying on SQL Server. Is it at all possible? ie to prevent other 3rd parties from conflicting your data.
Q3. (Last one) Since the coldfusion server is an occasionally connected client in many ways, has anyone else here had to do data comparisons before committing data to the DB?
In that you "get" the data, store in in session scope, then before you are about to update your new data, it compares the original set with the one in the DB, if a field is out of sync, it throws an exception/error. (That or timestamp the table?)
Anyones input on this would be appreciated, no matter how stupid or crazy your ideas maybe, have a crack :)
Scott
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
