On Sat, Jul 30, 2011 at 5:29 PM, Mike Copeland <[email protected]> wrote:
What version, what engines? Different engines have different features. > > This only happens on one form that DOES do a table lock, to obtain a > sequential document number. Here's psuedo-code... > > lock tables systemtable write > > select docid from systemtable > > update systemtable set docid=docid+1 > > unlock tables You're working too hard creating locks when you don't need to. Try deleting both the lock and unlock and try this as a single-user to confirm that the errors in the following lines go away. Then, try some of the alternate suggestions here: http://dev.mysql.com/doc/refman/5.0/en/innodb-locking-reads.html My preferences would be a single column docid table with autoincrementing primary key. Let the engine do the hard work. Create a record every time you need one. If you care, truncate the table once in a while to keep the size under control. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CACW6n4vQrdrHCqM=ip8o-shtgeycsf3yn90qqqsrqkbz19i...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
