Ali Awan wrote:
>
> In one case, I found concurrent queries and I also found 2 sessions hitting
> the same table.
If the concurrent queries do not lock the records in the same order as
the transaction does, that can cause deadlocks.
>> It is not unlikely this can deadlock, but to be certain w
Yes and no.
In one case, I found concurrent queries and I also found 2 sessions hitting the
same table.
>Did you find any concurrent queries?
>For a deadlock you need at least two SQL sessions hitting the same object.
>
>
>
>It is not unlikely this can deadlock, but to be certain we need to see
Ali Awan wrote:
> Every once in a while on my intranet application I get Database errors.
> MS SQL Server will throw an error that the transaction was deadlocked.
>
> It happens around a piece of code in which I have 2 queries, an Update and a
> Delete which are nested inside a CFTransaction.
> O
Ben,
I'm doing an exclusive lock.
>What kind of lock are you doing?
>
>Scope/name/exclusive?
>
>
>.
>Ben Nadel
>Certified Advanced ColdFusion MX7 Developer
>www.bennadel.com
~|
Deploy Web Applications Quickly
, 2007 4:55 PM
To: CF-Talk
Subject: Using CFLock around a query
The main question is: Is it ok to put a CFLock around one or more
cfqueries that are nested in a Cftransaction.
E.G.:
update table1
yadda yadda
Every once in a while on my intranet application I get Database errors.
MS SQL Server will throw an error that the transaction was deadlocked.
It happens around a piece of code in which I have 2 queries, an Update and a
Delete which are nested inside a CFTransaction.
It also happens on ano
file using cffile, I try to wrap the tag in a lock
like this...
Then I use a readonly lock whenever I read from the file.
-Original Message-
From: David Schmidt [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 14, 2002 10:42 AM
To: CF-Talk
Subject: using cflock with scope vs name
> Is there a benefit to use the name= attribute rather than
> the scope= attribute in a cflock statement. What is
> recommended?
If you're locking memory variables (Session, Application, Server) on CF
4.5.x or 5, I'd recommend using the SCOPE attribute. If you're locking
something else, or you'
Is there a benefit to use the name= attribute rather than the scope=
attribute in a cflock statement. What is recommended?
Thanks,
Dave
__
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.
> Good answer... makes sense... officially it conflicts with Allaire's
> recomendation, but I think you are correct.
Allaire has changed their recommendation since CF 4.5 came out, and their
recommendation has certainly been a moving target. The current
recommendation is to use it for all memory
: [EMAIL PROTECTED]
Subject: RE: Using CFLOCK
Paul Smith wrote:
>How do you output its value?
>
>>session.sessionid is a value which is set by the CF server, not by the
user,
Session and application variables are stored as structures, so you
can view them by looping through the str
Paul Smith wrote:
>How do you output its value?
>
>>session.sessionid is a value which is set by the CF server, not by the user,
Session and application variables are stored as structures, so you
can view them by looping through the structure. Just add this bit of
code to a page and it will o
It's a variable like any other, so:
#session.sessionid#
> -Original Message-
> From: paul smith [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 29, 2000 1:48 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Using CFLOCK
>
>
> How do you output its value?
>
How do you output its value?
best, paul
At 01:01 PM 3/29/2000 -0800, you wrote:
>session.sessionid is a value which is set by the CF server, not by the user,
--
Archives: http://www.eGroups.com/list/cf-talk
To Unsubs
ge-
> From: Cameron Childress [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 29, 2000 1:37 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Using CFLOCK
>
>
> Good answer... makes sense... officially it conflicts with Allaire's
> recomendation, but I think you are corr
L PROTECTED]]
> Sent: Wednesday, March 29, 2000 4:01 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Using CFLOCK
>
>
> session.sessionid is a value which is set by the CF server, not
> by the user,
> and is based on the CFID and CFToken cookies. It's initialized at the
>
lates the rules followed by CF server 4.5 when you
turn on "Automatic read locking" in CF Server Administrator.
> -Original Message-
> From: Cameron Childress [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 29, 2000 11:54 AM
> To: [EMAIL PROTECTED]
> Subject: R
> -Original Message-
> From: David Gassner [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 29, 2000 2:31 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Using CFLOCK
>
>
> If you are locking session vars, use the name:
>
> name="#session.sessionid#"
>
>
March 29, 2000 10:48 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Using CFLOCK
>
>
> > When using CFLOCK how important is it to name the lock
>
> In CF 4.0: very, always name it... In CF 4.5, which I am not
> using yet, I am
> uncertain if names should be used or not. In
> When using CFLOCK how important is it to name the lock
In CF 4.0: very, always name it... In CF 4.5, which I am not using yet, I am
uncertain if names should be used or not. In 4.5, I *think* they should be
used in all cases except for when locking application, session and server
v
When using CFLOCK how important is it to name the lock
and if you name all locks should everylock in your application
have a different name?
Thanks.
-- Ric Smith
--
Archives: http://www.eGroups.com/list/cf-talk
To
21 matches
Mail list logo
