Re: Alternative MySQL PEAR DB sequence behavior

From: Date: Sun, 22 Jul 2001 18:54:43 +0000
Subject: Re: Alternative MySQL PEAR DB sequence behavior
References: 1 2 3 4  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-983@lists.php.net to get a copy of this message
Stig.Bakken@fast.no (Stig S. Bakken) wrote in news:3B5B29DF.91292DDD@fast.no: > If there are any race conditions in the conversion from old to new > sequence (mysql implementation), I guess a table lock or something > should be applied? Uh oh, just as I began implementing LOCK TABLES during the conversion, I realized that we really should not it because LOCK TABLES unlocks all previous locked tables and commits any active transactions. This will mess up any application that attempts to retrieve the next ID during a transaction or if it locked some other tables in the system. I'm thinking of ways how to eliminate race conditions and not break any table locks or transactions. - Oleg

« previous php.pear.dev (#983) next »