List:Commits« Previous MessageNext Message »
From:Sergei Golubchik Date:June 30 2007 7:22pm
Subject:Re: bk commit into 5.1 tree (gkodinov:1.2519) BUG#29157
View as plain text  
Hi!

On Jun 30, Georgi Kodinov wrote:
> Serg,
> 
> On 29.06.2007, at 21:24, Sergei Golubchik wrote:
> 
> >when you're done, please change the status of a bug from Documenting
> >to Verified, set category to InnoDB, and add a comment explaining
> >why it cannot be fixed on MySQL side and how it can be fixed in
> >InnoDB.
> 
> Isn't it better to open up a new bug instead ?

Generally, yes, I tend to agree with it.
But in this case, I think, no - not better.
Bug's synopsys says "UPDATE, changed rows incorrect", description is
about UPDATE of InnoDB table reporting "changed rows" incorrectly.
This bug wasn't fixed by your commit, you only added a provision for a
fix. There were no user-visible changes in your patch.

Regards / Mit vielen Grüssen,
Sergei

-- 
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /   Sergei Golubchik <serg@stripped>
 / /|_/ / // /\ \/ /_/ / /__  Principal Software Developer
/_/  /_/\_, /___/\___\_\___/  MySQL GmbH, Radlkoferstr. 2, D-81373 München
       <___/                  Geschäftsführer: Kaj Arnö - HRB
München 162140
Thread
bk commit into 5.1 tree (gkodinov:1.2519) BUG#29157kgeorge28 Jun
  • Re: bk commit into 5.1 tree (gkodinov:1.2519) BUG#29157Sergei Golubchik29 Jun
    • Re: bk commit into 5.1 tree (gkodinov:1.2519) BUG#29157Georgi Kodinov30 Jun
      • Re: bk commit into 5.1 tree (gkodinov:1.2519) BUG#29157Sergei Golubchik30 Jun
        • Re: bk commit into 5.1 tree (gkodinov:1.2519) BUG#29157Georgi Kodinov2 Jul