100% of the time. If you follow the link to the <cflock> devnet article
from the URL I posted, it explains this. I'm not disputing what you
mentioned about the use of stored procedure special variables - that is also
very safe.
~Simon
Simon Horwith
CTO, Etrilogy Ltd.
Member of Team Macromedia
Macromedia Certified Instructor
Certified Advanced ColdFusion MX Developer
Certified Flash MX Developer
CFDJList - List Administrator
http://www.how2cf.com/
-----Original Message-----
From: Jochem van Dieten [mailto:[EMAIL PROTECTED]
Sent: 01 February 2004 15:56
To: CF-Talk
Subject: RE: CFLOCK:....Sunday (still not left computer all weekend,
flatmates will start thinking i have problems)
Simon Horwith said:
> 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]
