Heikki Tuuri writes:
> Jon,
>
> - Original Message -
> From: ""Jon Frisby"" <[EMAIL PROTECTED]>
> Newsgroups: mailing.database.mysql
> Sent: Saturday, June 22, 2002 12:51 AM
> Subject: Nasty LIMIT/multi-table DELETE bug?
>
>
>
A very nasty bug in multi-table deletes & updates)
Regards,
Jocelyn
- Original Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, June 22, 2002 12:16 AM
Subject: Re: Nasty L
Jon,
- Original Message -
From: ""Jon Frisby"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Saturday, June 22, 2002 12:51 AM
Subject: Nasty LIMIT/multi-table DELETE bug?
> I just discovered a very scary behavior. We're using MySQL
I just discovered a very scary behavior. We're using MySQL 4.0.1 on Linux,
both tables are InnoDB, AUTO_COMMIT is on (default) and these queries are
being issues from the MySQL interactive console.
If I do a query of the form:
SELECT
transaction_report.*,
confirmed
FROM
transaction_
Hi!
I still can not reproduce your case.
I first ran this script:
create database xx;
use xx;
CREATE TABLE `t1` (
`titre` char(80) NOT NULL default '',
`numeropost` mediumint(8) unsigned NOT NULL auto_increment,
`ouvert` tinyint(1) unsigned NOT NULL default '1',
`date` datetime N
Hi!
Thank you for your test case.
However, with latest 4.0.2 code I am getting correct results with
it. Difference in number of rows in select and delete are stemming
from the fact that select reports number of rows in result set, while
delete reports total number of rows deleted.
These are r
- Original Message -
From: "Jocelyn Fournier" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, May 25, 2002 3:35 PM
Subject: Re: multi-table delete bug
Hi,
Yes, you're right, but to see
