Serg,
On 30.06.2007, at 22:22, Sergei Golubchik wrote:
> 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.
Done as requested.
Best Regards,
Joro
--
Georgi Kodinov, Senior Software Engineer
MySQL AB, Plovdiv, Bulgaria, www.mysql.com
Office: +359 32 634 397 Mobile: +359 887 700 566 Skype: georgekodinov
Are you MySQL certified? www.mysql.com/certification
