That's a good thought...now we've got too much locking. The older versions
of Access used to lock sets of rows (known as pages), I think SQL 6.5 did
something like that also. I'm working with Sybase at the moment and will
need to check on that aspect of Sybase.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 11, 2000 12:31 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: Idea? (Don't read it Marc.)
One new wrinkle with DB-based client vars is whether your DB enables
row-level locking. SQL7 does, SQL6.5 does not (I think). Access probably
not. Others?
If your DB does not enable row level locking, it appears locking var1 can
also lock var2. Is there a scenario where this feature could cause a
*serious* CF problem? I can't see it (but then again, there's lots I can't
see ;-)
Yes? No?
best, paul
At 12:01 PM 10/11/00 -0500, you wrote:
>Since database-driven client variables are specific to a client session
only
>one request will try to read/update the information in that record (row) of
>the database.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
