Actually, it was not the 9.0 driver doing this but the one which bundled with the 9.0 windows server release (one click installer from enterprise db).So the fix in
8.4.0101 was not in that install kit. SQL_DBMS_NAME=17, 20, "PostgreSQL"
SQL_DBMS_VER=18, 12, "9.0rc1"
SQL_DEFAULT_TXN_ISOLATION=26, 4, SQL_TXN_READ_COMMITTED = 2
SQL_DESCRIBE_PARAMETER=10002, 2, "N"
SQL_DM_VER=171, 30, "03.52.1132.0000"
SQL_DRIVER_HDBC=3, 4, 0x013C4830
SQL_DRIVER_HDESC=135, 4, 0x013C9728
SQL_DRIVER_HENV=4, 4, 0x013C2940
SQL_DRIVER_HLIB=76, 4, 0x01300000
SQL_DRIVER_HSTMT=5, 4, 0x013C96C0
SQL_DRIVER_NAME=6, 30, "PSQLODBC35W.DLL"
SQL_DRIVER_ODBC_VER=77, 10, "03.51"
SQL_DRIVER_VER=7, 20, "08.04.0200"
vs
SQL_DATABASE_NAME=16, 16, "postgres"
SQL_DBMS_NAME=17, 20, "PostgreSQL"
SQL_DBMS_VER=18, 12, "9.0rc1"
SQL_DEFAULT_TXN_ISOLATION=26, 4, SQL_TXN_READ_COMMITTED = 2
SQL_DESCRIBE_PARAMETER=10002, 2, "N"
SQL_DM_VER=171, 30, "03.52.1132.0000"
SQL_DRIVER_HDBC=3, 4, 0x014E4930
SQL_DRIVER_HDESC=135, 4, 0x014E95D0
SQL_DRIVER_HENV=4, 4, 0x014E2940
SQL_DRIVER_HLIB=76, 4, 0x01450000
SQL_DRIVER_HSTMT=5, 4, 0x014E9568
SQL_DRIVER_NAME=6, 30, "PSQLODBC35W.DLL"
SQL_DRIVER_ODBC_VER=77, 10, "03.51"
SQL_DRIVER_VER=7, 20, "09.00.0101"
On Wed, Oct 27, 2010 at 8:47 AM, the6campbells
<the6campbells@gmail.com> wrote:
This is issue was reported previously and fixed in 8.4.0101 but see it in the 9.0 driver.
with t_cte ( cte1,cte2,cte3 ) as ( select tset1.rnum, tset1.c1, tset1.c2 from tset1 ) select * from t_cte
SQLPrepare:
In: StatementHandle = 0x00841B38, StatementText = "with t_cte ( cte1,cte2,cte3 ) as ( select tset1.rn...", TextLength = 105
Return: SQL_SUCCESS=0
SQLNumResultCols:
In: StatementHandle = 0x00841B38, ColumnCountPtr = 0x00095428
Return: SQL_SUCCESS=0
Out: *ColumnCountPtr = 0
