Is there anyway that I can get Query Browser to reinitialise it's connection to the database without restarting?
I've been playing with MySQL 5.0.13 and everytime I crash the server I have to restart Query Browser before I can continue which is annoying to say the least. At least the CLI client reconnects after failure, pity it's so bloody awkward to edit SP's with:- CALL Fail1(); ERROR 2006 (HY000): MySQL server has gone away No connection. Trying to reconnect... Connection id: 2 Also, what plans are there for Trigger support in Query Browser? Whilst I can create triggers happily in QB there's no indication that they exist on a table nor any facility to edit them? -- Best regards, Rob Hall - Red Hat Certified Engineer Technical Team Leader Newsquest Digital Media -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]