Re: Errors with nulls thru ODBC

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Johann Zuschlag <zuschlag2(at)online(dot)de>
Cc: pgsql-odbc <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Errors with nulls thru ODBC
Date: 2001-12-07 01:01:52
Message-ID: 3C101500.8842447D@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

> Johann Zuschlag wrote:
>
> Hi,
>
> I found a funny behavior using psqlodbc (07.01.0009) with PostgeSQL
> 7.1.3. An application shows eratic results in columns with smallint
> and int when there is no value defined, i.e. null, unknown. Sometimes
> I get a 1, 3, 5, 0, or nothing (smallint).
>
> The app is just doing a simple SELECT. There is no =null or similiar.
> I went thru all mails concerning null, isnull etc. I guess the problem
> is with the driver, not with postgreSQL. If I compare the same app
> with MSSQL I get the correct results, i.e. nothing. ;-)

Could you send me the Mylog output ?

regards,
Hiroshi Inoue

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message Hiroshi Inoue 2001-12-07 01:46:30 Re: Trouble with LargeObjects and ODBC, backend crash?
Previous Message Johann Zuschlag 2001-12-06 23:56:33 Errors with nulls thru ODBC