Bug #26916 MyODBC error messages not meaningful
Submitted: 7 Mar 2007 12:05 Modified: 10 Jul 2007 5:47
Reporter: [ name withheld ] Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:5.00.11 OS:Windows (Windows XP)
Assigned to: Jess Balint CPU Architecture:Any

[7 Mar 2007 12:05] [ name withheld ]
Description:
When trying to export a table from Microsoft Access 2000 into a MySQL 5.0.27 database with an existing table of the same name, it reports "[MySQL][MyODBC 5.00.11] Driver not capable (#0)".

How to repeat:
Create a Microsoft Access 2000 database with a table named "test". Create an ODBC connection to MySQL's "test" database. Create a "test" table in MySQL's "test" database.

Open the Microsoft Access 2000 database, try to export the "test" table, using the same target destination name, to the MySQL database. It will report "[MySQL][MyODBC 5.00.11] Driver not capable (#0)".

Suggested fix:
A more meaningful error message like piping the server's error message of "Error 1050 (42S01): Table `test` already exists" would be more useful.
[7 Mar 2007 14:56] Jess Balint
Can you let me know which version of Windows and Access? Also, what columns have you included in your 'test' table in Access?

Thanks!
[7 Apr 2007 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".
[10 Apr 2007 16:01] Valeriy Kravchuk
Feedback is still needed.
[10 Apr 2007 18:09] Jess Balint
Fix committed in rev 856. Access was only displaying the first diagnostic message and was useless due to missing conversion info for wide-string types. I added the conversion info, and now the error is displayed as expected:

DIAG [S1000] [MySQL][MyODBC 5.00.12][MySQL] 1050 Table 'x' already exists (1050)