Estoy tomando el sol
.
q
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Estoy tomando el sol
.
q
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
m forwarding this to Sanja.
IMHO current behaviour is absolutly correct.
Mikhail.
- Original Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 24, 2003 11:43 PM
Subject: Re: InnoDB locking: Different behavior on 3.23.55
Message -
From: ""Mikhail Entaltsev"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Thursday, July 24, 2003 3:44 PM
Subject: InnoDB locking: Different behavior on 3.23.55 and 4.0.13
> --=_NextPart_000_0119_01C351F2.03137C50
> Content-Typ
Hi
I have 2 MySQL servers:
Server1 is 3.23.55-max-log
Server2 is 4.0.13-standard-log
Let's assume that we have 2 connections (Conn1 and Conn2) and table test:
CREATE TABLE `test` (
`id` int(3) NOT NULL auto_increment,
`name` char(
