Bug #12422 | Changing DECIMAL values fails | ||
---|---|---|---|
Submitted: | 7 Aug 2005 21:35 | Modified: | 7 Dec 2006 7:58 |
Reporter: | Markus Popp | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S3 (Non-critical) |
Version: | 1.2.4 beta | OS: | Windows (Windows) |
Assigned to: | Mike Lischke | CPU Architecture: | Any |
[7 Aug 2005 21:35]
Markus Popp
[8 Aug 2005 6:51]
Aleksey Kishkin
tested against mysql 5.0.10beta-nt and qb 1.1.13 and didn't get any error. What server did you use? And what's your locale (I guess difference could be in the decimal point settings)?
[8 Aug 2005 6:58]
Markus Popp
The server version ist 4.1.13-nt. My location is Austria, however, I have default settings and the period is working in all the other clients as decimal seperator, except QueryBrowser. I have tested this example once more, now I'm getting the error message 'Invalid utf8 character string'. utf8 is the default character set on the system, maybe the problem relates to this.
[30 Aug 2005 21:10]
Jorge del Conde
Hi! I was unable to reproduce this bug using QB 1.1.14
[6 Oct 2006 18:48]
Markus Popp
This issue is back in 1.2.4-beta. If I try to change a decimal field it fails with the error message: "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' ('UNKNOWN','DRAWING','AUDIO','VIDEO','MULTIMEDIA','OFFICE','TEXT','EXE' at line 1"
[11 Oct 2006 17:18]
Sveta Smirnova
I can repeat the issue with message "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE `id`='2'' at line 1" Tried with both "." and "," signs.
[9 Nov 2006 14:14]
Hwa Siang KOK
What is the progress on this bug?
[6 Dec 2006 18:10]
Markus Popp
I did not find this bug in r6 anymore, may it have been fixed already?
[7 Dec 2006 2:42]
Hwa Siang KOK
Yes, it seems to have been fixed since r5.
[7 Dec 2006 7:58]
Mike Lischke
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at http://www.mysql.com/downloads/ PS: Thank you for checking this against the latest version. Works well for me too now.