Bug #7097 | false result calling a query through history | ||
---|---|---|---|
Submitted: | 8 Dec 2004 9:03 | Modified: | 16 Feb 2005 9:37 |
Reporter: | Oliver Peters | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S3 (Non-critical) |
Version: | 1.1.2 - 1.1.5 | OS: | Windows (Windows2000) |
Assigned to: | CPU Architecture: | Any |
[8 Dec 2004 9:03]
Oliver Peters
[8 Dec 2004 20:40]
MySQL Verification Team
Hi, I can't reproduce it with my queries. Do you get wrong SELECT statement in the History tab or in the query window?
[9 Dec 2004 12:36]
Oliver Peters
Hello, sorry, here a little more precise: I get the wrong result in the SQL Query Area - the history seems o.k. It's the difference between: "SELECT * FROM play;" and "SELECT * FROM play ;" nasty little difference ;-)
[14 Feb 2005 22:54]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[16 Feb 2005 9:37]
Oliver Peters
SELECT * FROM table ; results in ELECT * FROM table ; if you call the query through the history but SELECT * FROM table; brings the correct result - so the error depends on the position of the ;