Bug #23626 | Linux QB 1.2.4rc builds invalid SQL statement when selecting columns | ||
---|---|---|---|
Submitted: | 25 Oct 2006 13:35 | Modified: | 18 Aug 2007 3:31 |
Reporter: | C L | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S3 (Non-critical) |
Version: | 1.2.4beta | OS: | Linux (Fedora Core 5) |
Assigned to: | Vladimir Kolesnikov | CPU Architecture: | Any |
[25 Oct 2006 13:35]
C L
[25 Oct 2006 17:42]
MySQL Verification Team
Thank you for the bug report. Verified on Suse 10.1.
[1 Dec 2006 11:01]
Vladimir Kolesnikov
Hi, How exactly do you do the selection - by double clicking on tree node or by dragging the node into query area, etc? Is this problem similar to #24672? If yes, then it was fixed and will be available in the next release. Dragging works for me as well.
[4 Dec 2006 16:07]
C L
>How exactly do you do the selection - by double clicking on tree node or by dragging the node into query area, etc? Double clicking on the tree node. >Is this problem similar to #24672? If yes, then it was fixed and will be available in the next release. Dragging works for me as well. The problem was similar in that the clicking method did not product the correct SQL statement. But the symptoms were clearly different between 1.2.4 and 1.2.5. 1.2.4 created a SQL statement, clearly wrong. 1.2.5 did not create a statement at all. Looking forward to the next release.
[22 Jan 2007 11:59]
Stefan Zingler
The same exists in Version 1.2.9rc for Windows XP. After select columns from the schema tree. Click or Drag & Drop results in the same error. Sample after two clicks: SELECT a., a.`mandatory` `name` FROM product_attributes p, attributes a WHERE p.attribute_id=a.attribute_id; It seems there is a problem with the cursor position.
[18 Aug 2007 3:31]
MySQL Verification Team
I wasn't able to repeat anymore with version 1.2.12.