Re: Bug in SQLColumns() and SQLTables() with "Parse Statement".

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: TANIDA Yutaka <tanida(at)sra(dot)co(dot)jp>
Cc: "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Bug in SQLColumns() and SQLTables() with "Parse Statement".
Date: 2003-11-10 07:15:50
Message-ID: 3FAF3B26.1FE0506E@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

TANIDA Yutaka wrote:
>
> Hi,
>
> I got a strange result when executing SQLColumns and SQLTables.
>
> 1. "Parse Statement" option turns on.
> 2. Connect to PostgreSQL by ODBC Driver.
> 3. Execute simple select statement by SQLExecDirect().
> 4. Execute SQLColumns().
> 5. Check all columns. It's same as select result of 3.
>
> Attached C program will reproduce this problem .If this option turns on ,
> You can see SQLNumResultCols() returns invalid column informations.
>
> Output of "Parse Statement" off.
> --
> 20
> 20
>
> Output of "Parse Statement" on.
> --
> 20
> 1

I've just committed a change to fix the above bug.
Please try the current CVS source or the latest snapshot dll at
http://www.geocities.jp/inocchichichi/psqlodbc/ .

Thanks.
Hiroshi Inoue
http://www.geocities.jp/inocchichichi/psqlodbc/

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Hiroshi Inoue 2003-11-10 07:20:50 Re: Help with hang on empty query (PG 7.3.2,
Previous Message Markus Wollny 2003-11-10 00:09:38 Re: S1010 function sequence error after ODBC-driver-upgrade