Re: mysqldump output file not valid as input file for mysql client

On Thu, 22 Feb 2001, Sinisa Milivojevic wrote: > Matt Loschert writes: > > On Thu, 22 Feb 2001, Sinisa Milivojevic wrote: > > > > > [EMAIL PROTECTED] writes: > > > > >Description: > > > > > > > > As of mysql 3.23.33, a dumpfile generated with mysqldump (using the >flags: > > > >

Re: mysqldump output file not valid as input file for mysql client

Matt Loschert writes: > On Thu, 22 Feb 2001, Sinisa Milivojevic wrote: > > > [EMAIL PROTECTED] writes: > > > >Description: > > > > > > As of mysql 3.23.33, a dumpfile generated with mysqldump (using the >flags: > > > --opt --all-databases) creates a file which will no

Re: mysqldump output file not valid as input file for mysql client

On Thu, 22 Feb 2001, Sinisa Milivojevic wrote: > [EMAIL PROTECTED] writes: > > >Description: > > > >As of mysql 3.23.33, a dumpfile generated with mysqldump (using the flags: > > --opt --all-databases) creates a file which will not be uploaded correctly > > using the mysq

Re: mysqldump output file not valid as input file for mysql client

[EMAIL PROTECTED] writes: > >Description: > > As of mysql 3.23.33, a dumpfile generated with mysqldump (using the flags: > --opt --all-databases) creates a file which will not be uploaded correctly > using the mysql client (as in: 'mysql -u root -pXX -q -s < >dumpf