Re: deadlocks in CFGLOBAL

2002-05-20 Thread Jon Hall
Client variables use a cookie to look up the client value from the database, so it is possible and I imagine cfglobal table gets a lot of Update or Select/Insert (I'm not sure how CF handles updating that table) queries under load. You might want to go into the CF admin and just disable global cli

RE: deadlocks in CFGLOBAL

2002-05-20 Thread Hoag, Claudia (LNG)
Thanks, I didn't realize that's all it was storing in CGLOBAL :) -Original Message- From: Jon Hall [mailto:[EMAIL PROTECTED]] Sent: Monday, May 20, 2002 12:38 PM To: CF-Talk Subject: Re: deadlocks in CFGLOBAL Client variables use a cookie to look up the client value from th

RE: deadlocks in CFGLOBAL

2002-05-20 Thread Bryan Love
Strange. Deadlocks most often happen when you have code that updates one row in the DB based on info from another row. Example: UPDATE cellGlobal SET myVar = (SELECT myVar from cellGlobal WHERE foo = 1) WHERE foo = 2; This code is dangerous because it could cause deadlocks... what if it's upda

RE: deadlocks in CFGLOBAL

2002-05-20 Thread Rob Baxter
PM To: CF-Talk Subject: RE: deadlocks in CFGLOBAL Thanks, I didn't realize that's all it was storing in CGLOBAL :) -Original Message- From: Jon Hall [mailto:[EMAIL PROTECTED]] Sent: Monday, May 20, 2002 12:38 PM To: CF-Talk Subject: Re: deadlocks in CFGLOBAL Client variables