| Bug #11351 | Default schama gets lost on connect after loss of db connection | ||
|---|---|---|---|
| Submitted: | 15 Jun 2005 13:09 | Modified: | 30 Jun 2005 14:05 |
| Reporter: | Kai Sautter (Basic Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Query Browser | Severity: | S3 (Non-critical) |
| Version: | 1.1.10 | OS: | Windows (Windows XP (SP2)) |
| Assigned to: | Vladimir Kolesnikov | CPU Architecture: | Any |
[16 Jun 2005 12:47]
Aleksey Kishkin
I tested this way: 1) started QB, connected to 'test' scheme 2) wrote some query in query window 3) choose in QB FILE-> reconnect and result - I lost my query 1) started QB 2) opened script tab 3) wrote some script 4) killed and restarted mysql server; 5) press 'continue' in toolbar -- got error message about mysql has gone away 6) chooce FILE->connect from menu -- connect dialog appears without default scheme
[30 Jun 2005 14:05]
Vladimir Kolesnikov
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.
If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information
about accessing the source trees is available at
http://www.mysql.com/doc/en/Installing_source_tree.html
Description: If the connection to the server gets lost an you have to connect again, after executing a scripts unsuccessfully, the default schema gets lost. If you do the same thing from a query tab, you only have the option to reconnect, which makes you lose all scripts and queries in the open tabs (if not saved). How to repeat: Starting point: The connection to the database server got lost. Executing the script results in an error ("Access Violation at address 00835064 in module 'LIBMYSQL.dll'. Read of address 0000025C"). Choose File | Connect and enter the password. Note on query tabs: If you do the same thing with a query the error message will be "Query Execute Thread cannot connect to MySQL", but you can only execute the function "reconnect", which is always available (except in the above sequence of commands). Suggested fix: (a) Queries and scripts should behave the same (the possibility to connect again while keeping your work is desirable) (b) The default schema should be kept (see command line utility)