Whatever you do, make sure that every bit of code that locks multiple resources locks them in the same order. That's the only way to avoid deadlocks.
Regards, Jerry Schwartz The Infoshop by Global Information Incorporated 195 Farmington Ave. Farmington, CT 06032 860.674.8796 / FAX: 860.674.8341 www.the-infoshop.com www.giiexpress.com www.etudes-marche.com > -----Original Message----- > From: David T. Ashley [mailto:[EMAIL PROTECTED] > Sent: Monday, June 04, 2007 3:54 PM > To: mysql@lists.mysql.com > Subject: Re: Lock Tables Question > > On 6/4/07, Gerald L. Clark <[EMAIL PROTECTED]> wrote: > > > > David T. Ashley wrote: > > >> > >> LOCK TABLE thistable, thattable, theothertable, > >> goshthislistcangetlongtable; > >> Do whatever is needed; > >> UNLOCK TABLES; > > >You could use a string lock for this. > > Thanks for the suggestion. It looks logically correct. > > I'd like to stay away from a string lock if possible because > other database > users could interfere with it (it is server global, and not > tied to the > database). > > My original question is still of interest to me ... > > Thanks. > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
