| Bug #5144 | User Variables Error in Query Browser | ||
|---|---|---|---|
| Submitted: | 22 Aug 2004 23:23 | Modified: | 27 Aug 2004 12:10 |
| Reporter: | C B | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Query Browser | Severity: | S2 (Serious) |
| Version: | 1.0.5-a | OS: | Windows (XP) |
| Assigned to: | Michael G. Zinner | CPU Architecture: | Any |
[22 Aug 2004 23:23]
C B
[23 Aug 2004 2:56]
Matthew Lord
Hi, Thanks for your bug report! I don't get the same error that you do but I do not get the correct results, I just get an empty string back. In any event, the related code needs to be looked at. Best Regards,
[23 Aug 2004 16:00]
C B
Forgot to include the MySQL server info: [root@ns1 ~]# mysql -V mysql Ver 12.22 Distrib 4.0.16, for pc-linux (i686) [root@ns1 ~]# uname -a Linux ns1.hostnamehidden 2.4.20-20.9 #1 Mon Aug 18 11:27:43 EDT 2003 i686 athlon i386 GNU/Linux
[27 Aug 2004 12:10]
Michael G. Zinner
QB makes use of multithreading so it is possible to e.g. do two selects at the same time or edit a table while a query is running. Therefore a now instance connection is opened to fetch the rows of a resultset and closed after all rows have been retrieved. Since @xxx server variables only work for the current connection, the value is not shown when doing a select. If you do not want this behaviour, start a transaction with the (>) button in the advanced toolbar. If a transaction is started everything is done with on connection. Please note that all other tasks will be on hold till a resultset has been fetched completely, since all features of the tool must share a single conenction. Another solution to this is use the GUI Command Line (see the View menu). This behaves like a standard mysql client and therefore should response as expected.
