Databases do this stuff for you; that's what transactional
database processing is all about. I'd strongly recommend using
transactions within the database to do this instead of CFLOCK.
how about cftransaction?
CFTRANSACTION allows CF to take advantage of transaction processing within
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I haven't seen anything yet that talks explicitly about when
to use the Name attribute and when to use the Scope
attribute. There have been a number of threads around
whether to single thread updates to a single table.
For example, lets
This clears it up a bit..
http://www.sys-con.com/coldfusion/archives/0208/Forta/index.html
-Original Message-
From: Andy [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 22, 2001 9:58 AM
To: CF-Talk
Subject: How to choose Name or Scope when locking
I haven't seen anything yet that
accessing it.
Hope that helps
Alistair Davidson
Senior Web Developer
Rocom
www.rocomx.net
-Original Message-
From: Zachary Bedell [mailto:[EMAIL PROTECTED]]
Sent: 22 February 2001 16:01
To: CF-Talk
Subject: RE: How to choose Name or Scope when locking
-BEGIN PGP SIGNED MESSAGE-
Hash
At 11:01 AM 02/22/2001 -0500, you wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I haven't seen anything yet that talks explicitly about when
to use the Name attribute and when to use the Scope
attribute. There have been a number of threads around
whether to single thread updates
CTED]
Sent: Thursday, February 22, 2001 10:01 AM
Subject: RE: How to choose Name or Scope when locking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I haven't seen anything yet that talks explicitly about when
to use the Name attribute and when to use the Scope
attribute. There have been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I haven't seen anything yet that talks explicitly about when to
use the Name attribute and when to use the Scope
attribute. There have been a number of threads around
whether to single thread updates to a single table.
For example,
First of all... Why in lord's name would you want to single
thread your DB access?
Fairly common example:
You insert something in the database, and immediately need to
access the ID of that new thing. You want to single thread the
insert and select, so the table doesn't change.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zac,
Thanks. This was very helpful.
One clarification question. Does a Named lock prevent a
same-named thread
within the session or application(on a single server?)?
Well... I'm not quite sure what you're asking.
The three scoped
on 2/22/01 2:13 PM, Dave Watts at [EMAIL PROTECTED] wrote:
Databases do this stuff for you; that's what transactional database
processing is all about. I'd strongly recommend using transactions within
the database to do this instead of CFLOCK. Of course, I suspect that you
already know this,
10 matches
Mail list logo
