Bug #31294 | Query Browser Is Unable to Use @Variables | ||
---|---|---|---|
Submitted: | 29 Sep 2007 17:50 | Modified: | 1 Oct 2007 13:18 |
Reporter: | Chris S | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S2 (Serious) |
Version: | 1.2.12 | OS: | Linux (Fedora 7) |
Assigned to: | CPU Architecture: | Any | |
Tags: | Query Browser declare @Variables |
[29 Sep 2007 17:50]
Chris S
[29 Sep 2007 18:11]
Chris S
This problem seems related to this thread in the forums: http://forums.mysql.com/read.php?108,62426,62426#msg-62426 Specifically, this remark by Mike Lischke: "It's a design flaw that will be corrected in the next major version of QB. It was thought as a means to make the application more flexible, but it did not entirely consider the way, how the MySQL server works." This post was over a year ago...
[1 Oct 2007 13:18]
MySQL Verification Team
Thank you for the bug report. By design QB creates a new connection for every query, then the variable isn't more valid for the new queries. That was already reported several times for this reason I am changing the status as duplicate.