Bug #36668 | Returned an E_FAIL status | ||
---|---|---|---|
Submitted: | 12 May 2008 14:52 | Modified: | 12 Jun 2008 18:27 |
Reporter: | Marcos Felipe Zara Zara | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 5.0.45-community-nt | OS: | Windows (XP SP2) |
Assigned to: | CPU Architecture: | Any |
[12 May 2008 14:52]
Marcos Felipe Zara Zara
[12 May 2008 15:03]
Valeriy Kravchuk
Thank you for a problem report. Please, upload the error log (<hostname>.err file in the data subdirectory usually), compressed, to the report. What exact version of Connector/ODBC do you use?
[12 May 2008 16:32]
Marcos Felipe Zara Zara
Error File
Attachment: Servidor2003.err (text/plain), 8.00 KiB.
[12 May 2008 16:33]
Marcos Felipe Zara Zara
OKs I sent the error file (servidor2003.err) I am using ODBC 3.51.12-win32
[12 May 2008 17:46]
Sveta Smirnova
Thank you for the report. There is "Version: '5.0.15-nt'" in the provided error log file, although you indicated 5.0.45 in the report. There are several bug reports related to DECIMAL column fixed since version 5.0.15. Please upgrade to current version 5.0.51a, try with it and inform us if problem still exists.
[12 May 2008 18:19]
Marcos Felipe Zara Zara
OKs. I have 2 clients running the same database(and having same problem). In one, I will try to upgrade to current version 5.0.51a and other I changed the field type from DECIMAL to DOUBLE ... Let's see what's will happen.!
[12 May 2008 18:27]
Sveta Smirnova
Thank you for the update. Please upgrade MySQL server, not only clients. We will wait feedback from you.
[12 Jun 2008 23:00]
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".