From: | "Glen Parker" <glenebob(at)nwlink(dot)com> |
---|---|
To: | <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Bug in latest ODBC driver (07.02.0004) |
Date: | 2002-11-22 05:26:18 |
Message-ID: | 002801c291e7$afd7e5f0$0b01a8c0@johnpark.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
The 07.02.0004 (the ver. 3, non unicode in this case) driver has broken
some programs I have. Attached is a snip from my ODBC log.
The basic problem seems to be that sending a 'create ...' statement to
the server and trying to get the row count after it executes causes
errors that shouldn't be happening. The statement executes fine, as the
log shows, but SQLRowCount() returns -1 (SQL_ERROR). There is also
aparently no error info saved because SQLGetDiagRecW() returns 100
(SQL_NO_DATA_FOUND).
Shouldn't SQLRowCount() succeed and return a row count of -1?
My platform is Win2k.
select version();
PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC 2.96
Glen Parker
glenebob(at)nwlink(dot)com
Attachment | Content-Type | Size |
---|---|---|
ODBC.log | application/octet-stream | 1.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2002-11-22 10:58:35 | Re: "#if (ODBCVER >= 0x0399)" in info.c? |
Previous Message | markw | 2002-11-22 03:57:14 | Very large queries with ODBC |