Re: DECIMAL col type bug in DBD::mysql w/mysql 5
Ray Zimmerman <[email protected]>
| Newsgroups | gmane.comp.db.mysql.perl |
|---|---|
| Message-ID | <[email protected]> |
FYI, it is currently a verified bug ... http://bugs.mysql.com/bug.php?id=15556 - Ray On Dec 12, 2005, at 7:26 PM, Patrick Galbraith wrote: > Ray, > > Thanks for reporting this - I'll look into this. > > kind regards, > > Patrick > > > Ray Zimmerman wrote: > >> On Dec 2, 2005, at 11:37 AM, Selke, Gisbert W. wrote: >> >>> I don't think it's DBD::mysql. http://bugs.mysql.com/bug.php? >>> id=14923 has an >>> entry from the MySQL people that may be an explanation. Base >>> line: "There is >>> no standard C type for fixed point numeric type, so MySQL server >>> returns decimal as a string." This comes also up in MySQL >>> QueryBrowser, so >>> it's not just DBD::mysql. >> >> >> While this may be related, I think it is a different issue. I'm >> not sure where the bug is (server or DBD::mysql), but apparently >> the server knows that the column is a DECIMAL type as opposed to >> VARCHAR, since SHOW COLUMNS FROM <table> does say DECIMAL. >> >> Whether or not the server returns values for decimal columns as >> strings is not the issue. It's the fact that when I query for the >> column type I'm being told it's a VARCHAR column, when it's >> actually a DECIMAL column. I still believe this is a bug, but >> without knowing how DBI sets these values, I don't know if it's a >> bug in the driver or in the server. >> >> Ray >> >> > -- MySQL Perl Mailing List For list archives: http://lists.mysql.com/perl To unsubscribe: http://lists.mysql.com/[email protected]