is supposed to wrap a group of querries that form a process.
Such as if someone was purchasing a product and three querries are used, one
to check the user/update user information, pull information from a shopping
cart, and submit the purchase data. you would lock each one of theese
querrys and
True, transactions are not supported in MySQL. A CFLOCK would not create a
database transaction, and would not provide some of the benefits of
transactions such as rollback, but in this case it would have a similar
effect of making sure that no-one else was generating a new ID at the same
time.
no, CFLOCK is only for restricting access to a server side variable. DBs
don't benefit from this.
chris olive, cio
cresco technologies
[EMAIL PROTECTED]
http://www.crescotech.com
-Original Message-
From: Bud [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 13, 2000 12:41 PM
To: CF
t: Re: cflock vs. cftransaction
is supposed to wrap a group of querries that form a process.
Such as if someone was purchasing a product and three querries are used, one
to check the user/update user information, pull information from a shopping
cart, and submit the purchase data. you would lock eac
Yes, but like he said .. transactions aren't supported my MySQL.
Todd Ashworth
- Original Message -
From: "Greg Wolfinger" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Wednesday, December 13, 2000 1:29 PM
Subject: Re: cflock vs. cft
CFLOCK doesn't provide the same effect as cftransaction. In MySQL you can
lock your tables, though. It's a little cumbersome. It basically means
that MySQl is only handling one request at a time... Here's some code that
Tage Widsell posted to this listserv earlier this month:
LOCK TABLES you
> no, CFLOCK is only for restricting access to a server side
> variable. DBs
> don't benefit from this.
No, CFLOCK restricts access to a chunk of code. The CFLOCK you suggested
should work, but won't you need to wrap READONLY CFLOCKs around every other
query for the database?
~
On 12/13/00, Evan Lavidor penned:
>CFLOCK doesn't provide the same effect as cftransaction. In MySQL you can
>lock your tables, though. It's a little cumbersome. It basically means
>that MySQl is only handling one request at a time... Here's some code that
>Tage Widsell posted to this listserv
al Message-
From: Christopher Olive, CIO [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 13, 2000 3:18 PM
To: CF-Talk
Subject: RE: cflock vs. cftransaction
no, CFLOCK is only for restricting access to a server side variable.
DBs
don't benefit from this.
chris olive, cio
cresco tech
9 matches
Mail list logo