sorry - you (and I in the article) are correct.  I got the tech note about
exclusive locks "solving" concurrency problems inside of non-serializable
transactions confused with a J2EE container bug surrounding transactional
processing in JRun.  The JRun bug fix is exactly as I described.  Thanks for
pointing that out, Dave.  It's not every day I am corrected by my own quote.
Now if I could just get this JRun bug to go away...

~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: Dave Watts [mailto:[EMAIL PROTECTED]
  Sent: 01 February 2004 23:41
  To: CF-Talk
  Subject: RE: CFLOCK:....Sunday (still not left computer all weekend, flatm
ates will start thinking i have problems)

  > even with serializable database transactions, the return is
  > not accurate 100% of the time. If you follow the link to the
  > <cflock> devnet article from the URL I posted, it explains this.

  According to that article:

  "Serializable isolation level transactions are the most data-consistent
  transactions, but also have the most overhead. A serializable transaction
  places an exclusive lock on every data-table in use for the duration of
the
  transaction. Essentially, access to database tables is single-threaded
when
  you use serializable transactions. Because serializable transactions use
the
  highest locking levels, best practices discourage using it."

  By that logic - your logic from the article you wrote - you should never
  need to use CFLOCK in conjunction with CFTRANSACTION to get the values you
  should. And, your logic was absolutely right! Here's part of what SQL
Server
  Books Online says about serializable transactions:

  "Places a range lock on the data set, preventing other users from updating
  or inserting rows into the data set until the transaction is complete."

  Dave Watts, CTO, Fig Leaf Software
  http://www.figleaf.com/
  voice: (202) 797-5496
  fax: (202) 797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to