11g ODBC SQLGetTypeInfo result COLUMN_SIZE column being returned as 64bit v

Question

Using InstantClient 11.2 ODBC I'm getting odd behavior for the SQLGetTypeInfo call on a 64bit Win2K3 machine.
When binding the result column 2 (COLUMN_SIZE) as an integer (as per the ODBC spec), it looks like this is being returned in a 64bit word (even though the buffer buffer size is specified as a SQLUINTEGER).
This is obviously causing some issues - is this a known bug?
My solution is to move this value's storage to the end of the struct I'm using to store all the columns of the result and add some additional padding but my concern is that there are other areas where the ODBC interface is not following the ODBC specification. Is there a list of known exceptions to the ODBC specification for the oracle instant client drivers for 64 bit architectures?

Answer 1

Thanks. That's doing the trick.
We can use PASSTHROUGH PACKAGE to change the SQL_MODE for a particular session using the MySQL statement: set session sql_mode='ANSI_QUOTES';
It will then look like:
- first setting in the session ANSI_SQL using PASSTHROUGH:
DECLARE
ret integer;
c integer;
BEGIN
c := DBMS_HS_PASSTHROUGH.OPEN_CURSOR@mysql;
DBMS_HS_PASSTHROUGH.PARSE@mysql(c, 'SET SESSION SQL_MODE=''ANSI_QUOTES'';'));
ret := DBMS_HS_PASSTHROUGH.EXECUTE_NON_QUERY@mysql(c);
dbms_output.put_line(ret ||' passthrough output');
DBMS_HS_PASSTHROUGH.CLOSE_CURSOR@mysql(c);
END;
REMARK: The passthrough statement SET SQL_MODE=''ANSI_QUOTES''; uses 2 single quotes ... !!no DOUBLE QUOTES !!
Now selects works using double qoutes:
SQL> select * from "test"@mysql;
col1 col2
Hello 1
As soon as I disconnect and connect again and try to run the select without the PASSTHROUGH we get the old error again:
SQL> select * from "test"@mysql;
select * from "test"@mysql
ERROR at line 1:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[MySQL][ODBC 3.51 Driver][mysqld-5.0.37-community]You have an error in your SQL
syntax; check the manual that corresponds to your MySQL server version for the
right syntax to use near '"col1",A1."col2" FROM "test" A1' at line 1
ORA-02063: preceding 2 lines from MYSQL
So using PASSTHROUGH at the beginning of each session allows us to change the ANSI mode for a particular session only without affecting all the other clients and might be a good workaround.