Bug #12411 Error inserint row from ACCESS 2000 in linux mysql
Submitted: 6 Aug 2005 10:00 Modified: 6 Aug 2005 12:50
Reporter: Adim Costa Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5.07 OS:Linux (Linux Fedora Core 3)
Assigned to: CPU Architecture:Any

[6 Aug 2005 10:00] Adim Costa
Description:
I'm developing an application using MS ACCESS 2000 and windows mysql server 5.07. ALL OK
But porting server to a Linux server (Fedora Core 3, Mysql server 5.07 32 bit linux rpm) I got error 3146 (odbc call error) from ODBC driver on a PassThrough query:

INSERT INTO Documento_contabile (ID_tipo_documento_contabile, Data_emissione, ID_numerazione, ID_anagrafica, ID_indirizzo, Indirizzo, ID_causale_affare, Protocollo, ID_previus) VALUES (5, '2005-8-6', 5, 0, 0, 'B.go Pinti 80 - 50121 Firenze (Fi)', 5, 5, 0); 

But this query work on window mysql server 5.07

Please help me

How to repeat:
Use query as reported
[6 Aug 2005 12:50] MySQL Verification Team
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.
[6 Aug 2005 13:57] Adim Costa
The problems is using a SQL PassThrough query in MS Access code from a client (windows XP SP2) to a dedicated server running msql server 5.07 (Linux fedora core 3):

The SQL string is: 
INSERT INTO Documento_contabile (ID_tipo_documento_contabile, Data_emissione, ID_numerazione, ID_anagrafica, ID_indirizzo, Indirizzo, ID_causale_affare, Protocollo, ID_previus) VALUES (5, '2005-8-6', 5, 0, 0, '0', 5, 5, 0); 

But I got same error with simpler INSERT INTO Statment, for example:
INSERT INTO Documento_contabile (ID_tipo_documento_contabile) VALUES (5); 

Strange behaviour ! Identical SQL PassThrough  query is OK if passed to a mysql server 5.07 windows version running on the client (localhost).

I Solved problem:
the table name "documento_contabile" not "Documento_contabile".
But under windows upper/lower filenames are identical !!!
Under linux no !!!
Silly problem !

But I think we need a better error handing (and reporting) by ODBC driver
TNX !