List:Bugs« Previous MessageNext Message »
From:Michael Widenius Date:April 22 2001 6:54am
Subject:Re: Bug in mysqlbinlog (win32)
View as plain text  
Hi!

>>>>> "Ze'ev" == Ze'ev Bubis <zeevb@stripped> writes:


Ze'ev> Timothy Smith wrote:
>> On 2001 Apr 20, Michael Widenius <monty@stripped> wrote:
>> >
>> > This is a bug in DOS and the only way to go around it is to let
>> > mysqldump create the file itself and not rely on redirect by DOS.
>> 
>> s/mysqldump/mysqlbinlog/
>> 
>> E.g.,
>> 
>> $ mysqlbinlog --result-file=filename hostname-bin.[0-9]*
>> 

Ze'ev> This does not work on NT, in fact it causes an Access Violation
Ze'ev> Exception.

Ze'ev> Here is the output from Dr. Watson:

Note first that mysqlbinlog doesn't have a --result-file=# argument.
In my previous email I just suggested that we should add such an
argument to next MySQL release.

(Sasha, can you please fix this ?)

The error you got shows that there is some bug when mysqlbinlog tries
to write an error message about the missing option. I have now fixed
this and this will also be in the next MySQL release.

Thanks for the bug report.

Regards,
Monty
Thread
Bug in mysqlbinlog (win32)Ze'ev Bubis18 Apr
  • Bug in mysqlbinlog (win32)Michael Widenius18 Apr
  • Re: Bug in mysqlbinlog (win32)Ze'ev Bubis20 Apr
    • Re: Bug in mysqlbinlog (win32)Michael Widenius20 Apr
      • Re: Bug in mysqlbinlog (win32)Timothy Smith20 Apr
  • Re: Bug in mysqlbinlog (win32)Ze'ev Bubis22 Apr
    • Re: Bug in mysqlbinlog (win32)Michael Widenius22 Apr
Re: Bug in mysqlbinlog (win32)Michael Widenius19 Apr