At 2:42 PM +0300 8/25/99, <sinisa@stripped> wrote:
> > >Description:
> > Watch this:
> > fisher:/usr/local/apache/cgi-mysql > mysql -u root -p
> > Enter password:
> > Welcome to the MySQL monitor. Commands end with ; or \g.
> > Your MySQL connection id is 2 to server version: 3.22.25
> > Type 'help' for help.
> > mysql> select * from blah;
> > ERROR 1046: No Database Selected
> > mysql> lock tables blah write;
> > ERROR 2013: Lost connection to MySQL server during query
> > mysql>
> > Whoops! The mysql client drops connecton on that command. Or perhaps the
> > mysql server itself does? Either way the connection really is dead at that
> > point. If you try to use a different database it will print the
> > reconnecting text. It's because I don't have a database context,
>if I issue
> > that command inside of a databse context (EG use whatever_db) it won't
> > crash.
> > >How-To-Repeat:
> > see above
> > >Fix:
>This is not a bug.
>You must select a database when issuing database related commands.
It's not a bug for the connection to the server to be lost
when a simple error occurs? Sure, there is an error in
what he's doing, but shouldn't you just get an error message
rather than losing the server?
Paul DuBois, paul@stripped