RE: Best way to do this query

2002-02-27 Thread Jeffrey Polaski
I'd suggest using a stored procedure with a transaction and do it in the database. CF is rather aggressive in how it locks the db, and this can lead to performance problems if the db gets a lot of use. SP's give you a performance boost, and aren't that hard to do, especially once you have the S

RE: Best way to do this query

2002-02-19 Thread Phillip Broussard
DOH! I need to get some fresh air because that was too obvious. Thanks all. Phillip > -Original Message- > From: C. Hatton Humphrey [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 19, 2002 2:13 PM > To: CF-Talk > Subject: RE: Best way to do this query > >

Re: Best way to do this query

2002-02-19 Thread NathanielHorwitz
I've faced this before and I usually use cflock to prevent 2 users from inserting the record at the same time. > Sorry to ask but I have a dead brain right now. (I hate it when I feel > dumb.) > > X¿x > ~~~ > > I need to check the database to see if a record is there. > If it's there then i

RE: Best way to do this query

2002-02-19 Thread C. Hatton Humphrey
Use CFLock. It will put the two people in a single file line when executing the code, removing the possibility of a double-hit. Hatton > -Original Message- > From: Phillip Broussard [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 19, 2002 3:03 PM > To: CF-Talk > Subject: Best way

RE: Best way to do this query

2002-02-19 Thread Shawn Kernes
just wrap it up in a cflock studio will give you the specifics -Original Message- From: Phillip Broussard [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 19, 2002 12:03 PM To: CF-Talk Subject: Best way to do this query Sorry to ask but I have a dead brain right now. (I hate it w

RE: Best way to do this query

2002-02-19 Thread Andrew Scott
Would a cftransaction be sufficient here, if you have the ability to maybe a stored procedure would be better. If not swap a cflock around the block of code should to the trick as well. -Original Message- From: Phillip Broussard [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 20 February 20