List:Commits« Previous MessageNext Message »
From:Ingo Strüwing Date:July 10 2007 2:44pm
Subject:Re: bk commit into 6.0-falcon tree (istruewing:1.2567) BUG#28158
View as plain text  
Hi Sergei,

Sergei Golubchik wrote:
...
> I'd expect this to be easy to trigger - e.g. multi-update, two tables,
> the second is updated (perhaps straigh join or another trick to ensure
> it's the *second*), and unique key violation.

This one did it:

CREATE TABLE t1 (a int, b int, KEY (a, b));
CREATE TABLE t2 (a int, b int, UNIQUE KEY (a, b));
INSERT ...
UPDATE t1, t2 SET t1.a = 1, t2.a = 1;

Thanks for the hint. And thanks for noticing this.
I'll add the test case and remove the purecov comments.

Regards
Ingo
-- 
Ingo Strüwing, Senior Software Developer
MySQL GmbH, Radlkoferstr. 2, D-81373 München
Geschäftsführer: Kaj Arnö - HRB München 162140
Thread
bk commit into 6.0-falcon tree (istruewing:1.2567) BUG#28158ingo4 Jul
  • Re: bk commit into 6.0-falcon tree (istruewing:1.2567) BUG#28158Sergei Golubchik9 Jul
    • Re: bk commit into 6.0-falcon tree (istruewing:1.2567) BUG#28158Ingo Strüwing10 Jul
      • Re: bk commit into 6.0-falcon tree (istruewing:1.2567) BUG#28158Sergei Golubchik10 Jul
        • Re: bk commit into 6.0-falcon tree (istruewing:1.2567) BUG#28158Ingo Strüwing10 Jul
        • Re: bk commit into 6.0-falcon tree (istruewing:1.2567) BUG#28158Ingo Strüwing10 Jul