Re: cope with deadlock

On 11/17/2011 01:41, 王科选 wrote: hi, From this url: http://dev.mysql.com/doc/refman/5.5/en/innodb-deadlocks.html , mysql says "If you are using locking reads (|SELECT ... FOR UPDATE| or|SELECT ... LOCK IN SHARE MODE|), try using a lower isolatio

RE: Read_only and InnoDB transactions

It may not have an impact on you, but be aware of this severe (imho) bug that caused read_pnly to be ignored regardless of running transactions in version 5.5.8. See bug#58669 and others. We upgraded to 5.5.17 where the bug was fixed. David. From: Viacheslav Biriu

Re: Read_only and InnoDB transactions

MySQL Community Server 5.1.59 on the Centos 5.7 2011/11/28 David Lerer > What version do you use? David. > > -Original Message- > From: Viacheslav Biriukov [mailto:v.v.biriu...@gmail.com] > Sent: Monday, November 28, 2011 7:09 AM > To: mysql@lists.mysql.com > Subject: Read_only and InnoD

RE: Read_only and InnoDB transactions

What version do you use? David. -Original Message- From: Viacheslav Biriukov [mailto:v.v.biriu...@gmail.com] Sent: Monday, November 28, 2011 7:09 AM To: mysql@lists.mysql.com Subject: Read_only and InnoDB transactions Hi all. >From the Mysql Documentation: If you attempt to enable read

Read_only and InnoDB transactions

Hi all. >From the Mysql Documentation: If you attempt to enable read_only while other clients hold explicit table > locks or have pending transactions, the attempt blocks until the locks are > released and the transactions end. While the attempt to enable read_only is > pending, requests by other

Re: "UPDATE" with variable

- Original Message - > From: "Halász Sándor" > > mysql> update address set membersince = (select membersince from > address where memberid = 1258) where memberid = 1724; IIRC, subselects are allowed, except for selects that reference the table you're updating. -- Bier met grenadyn Is a