From: | Barry Cohen <bcohen(at)usdata(dot)com> |
---|---|
To: | 'Hiroshi Inoue' <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | "'pgsql-odbc(at)postgresql(dot)org'" <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: SQLParamOptions(): Incorrect base for returned row. |
Date: | 2002-10-29 18:26:26 |
Message-ID: | 7AE316508068D311BE7700A0C9B6BA550284B740@EXCH_CLUSTER |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Yes. This seems to resolve the problem.
-----Original Message-----
From: Hiroshi Inoue [mailto:Inoue(at)tpf(dot)co(dot)jp]
Sent: Tuesday, October 29, 2002 4:43 AM
To: Barry Cohen
Cc: 'pgsql-odbc(at)postgresql(dot)org'
Subject: Re: [ODBC] SQLParamOptions(): Incorrect base for returned row.
Barry Cohen wrote:
>
> Yes. The index problem seems to only occur during an error case.
>
> If all rows are successfully inserted, then 'pirow' equals 'crow',
> which is correct.
>
> The index problem occurs for error encountered during block inserts,
> deletes, and updates.
Please try the snapshot dll at http://w2422.nsk.ne.jp/~inoue/.
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/
From | Date | Subject | |
---|---|---|---|
Next Message | Alain Remont | 2002-10-31 01:21:34 | #Deleted |
Previous Message | Hiroshi Inoue | 2002-10-29 10:43:16 | Re: SQLParamOptions(): Incorrect base for returned row. |