| Bug #55824 | Option or compatibility mode for mysqldump to NOT quote decimal values | ||
|---|---|---|---|
| Submitted: | 8 Aug 2010 16:40 | Modified: | 16 Dec 2010 8:34 |
| Reporter: | Valeriy Kravchuk | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: mysqldump Command-line Client | Severity: | S3 (Non-critical) |
| Version: | 5.1+ | OS: | Any |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | mysqldump, regression | ||
[8 Aug 2010 16:40]
Valeriy Kravchuk
[15 Dec 2010 19:30]
Peter Gulutzan
In an earlier private comment I said this doesn't
happen in 5.5. That's technically true, but the
relevant code in mysqldump is:
if (field->type == MYSQL_TYPE_DECIMAL)
{
/* add " signs around */
dynstr_append_checked(&extended_row, "'");
dynstr_append_checked(&extended_row, ptr);
dynstr_append_checked(&extended_row, "'");
}
else
dynstr_append_checked(&extended_row, ptr);
and in this recently-created table
field->type is not MYSQL_TYPE_DECIMAL,
it is MYSQL_TYPE_NEWDECIMAL.
Two possibly related bugs.mysql.com items are:
Bug#2005 Long decimal comparison bug
(this might be the reason for the ''s).
Bug#58878 UPDATE fails when DECIMAL column value is quoted
(this might be due to qt3 adding quotes as mysqldump does).
[16 Dec 2010 8:34]
Georgi Kodinov
FIxed by the fix for bug #42980
