> actually, the use of <cflock> and <cftransaction> together is the
> recommended practice... under extremely heavy load <cftransaction>
> doesn't return the proper unique id to the client 100% of the time
Make the transaction serializable.
> but <cflock> does.
Only if CF is the only application manipulating the database and you
have only one instance of CF running.
If your database provides a native mechanism for returning inserted
keys (@@identity, last_inserted_id(), lastval() etc.), use that.
Jochem
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
