From: | Rainer Bauer <usenet(at)munnin(dot)com> |
---|---|
To: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: Snapshot 08.01.0006 available for testing |
Date: | 2005-11-03 15:49:38 |
Message-ID: | djakm11c88jn5fim2l31mnbbp0o06sfe7g@4ax.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
"Dave Page" schrieb:
>Please take some time to download and test this release, and report any
>regressions from prior snapshots as soon as possible.
I just installed the pgsql and psqlodbc RC1, but "UseServerSidePrepare" is
still broken.
SQL command: "SELECT col1 FROM table WHERE col2=?"
(Note: col1 is a SERIAL, col2 a VARCHAR).
Bind the input [SQLBindParameter] and output [SQLBindCol] parameter before
calling SQLPrepare().
The following call to SQLExecute() returns SQL_SUCCESS. But the first call to
SQLFetch() produces this error message:
<1> {HY010}(3) Null statement result in PGAPI_ExtendedFetch.
If I set "UseServerSidePrepare" to "0", everything works fine.
Using the debugger, I found out that Exec_with_parameters_resolved() will not
call SC_set_Curres(), because stmt->inaccurate_result and
conn->connInfo.disallow_premature are both FALSE.
However, the connections string I use (see below) did work with the "old"
psqlodbc driver 8.00.0102 that I used initially.
Let me know, if I can do anything else to help tracking down this bug.
Rainer
PS: This is my connection setting:
A0=0;A1=6.4;A2=0;A3=0;A4=0;A5=0;A6=;A7=100;A8=8192;A9=0;
B0=254;B1=4095;B2=0;B3=0;B4=1;B5=1;B6=0;B7=1;B8=0;B9=0;
C0=0;C1=0;C2=dd_;C3=0;C4=0;
Lie=0;LFConversion=0;TrueIsMinus1=0;BI=0;ByteaAsLongVarBinary=1;UseServerSidePrepare=1;LowerCaseIdentifier=0;
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2005-11-03 16:13:02 | Re: Snapshot 08.01.0006 available for testing |
Previous Message | Dave Page | 2005-11-03 15:44:04 | Re: Snapshot 08.01.0006 available for testing |