List:Commits« Previous MessageNext Message »
From:Øystein Grøvlen Date:October 21 2008 10:06am
Subject:Re: bzr commit into mysql-6.0-backup branch (oystein.grovlen:2707)
Bug#38810
View as plain text  
Øystein Grøvlen wrote:
> Chuck Bell wrote:
>> STATUS
>> ------
>> Clarification requested. Patch approval pending explanation of suppressed
>> warning.
>>
>> REQUESTS
>> --------
>> There are suppressed events as a result of this patch. Executing the test
>> case in the bug report after the patch shows the patch fixes the 
>> problem but
>> examination of warnings shows there are warnings that are not reported to
>> the user. Is this correct? If the warning is supposed to be 
>> suppressed, why
>> does SHOW WARNINGS display it?
> 
> I think this is a separate issue.  I get this warning regardless of name 
> and whether triggers are also defined.  It seems to me that restoring 
> any database with events will cause this warning to happen.  I will open 
> a separate bug for that.

I have file BUG#40197 for this issue.

--
Øystein

> 
> I also note that when I run the restore command there is no output that 
> indicates any warning.  Is that how it is supposed to be?  When I get 
> warnings with create table it says so.  E.g,:
> 
> mysql> create table test.t (i integer) engine=innodb;
> Query OK, 0 rows affected, 2 warnings (0.00 sec)
> 
> Any reason restore should be different?
> 
> -- 
> Øystein

Thread
bzr commit into mysql-6.0-backup branch (oystein.grovlen:2707)Bug#38810Oystein.Grovlen13 Oct
  • Re: bzr commit into mysql-6.0-backup branch (oystein.grovlen:2707)Bug#38810Rafal Somla13 Oct
    • Re: bzr commit into mysql-6.0-backup branch (oystein.grovlen:2707)Bug#38810Øystein Grøvlen14 Oct
  • RE: bzr commit into mysql-6.0-backup branch (oystein.grovlen:2707)Bug#38810Chuck Bell20 Oct
    • Re: bzr commit into mysql-6.0-backup branch (oystein.grovlen:2707)Bug#38810Øystein Grøvlen21 Oct
      • Re: bzr commit into mysql-6.0-backup branch (oystein.grovlen:2707)Bug#38810Øystein Grøvlen21 Oct