Re: PsqlODBC broken due to int4out(usesysid)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: prlw1(at)cam(dot)ac(dot)uk
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: PsqlODBC broken due to int4out(usesysid)
Date: 2000-10-02 17:10:47
Message-ID: 4979.970506647@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> writes:
> Reason: AFAICT it really doesn't want "int4out"..

Yup, the odbc driver is already fixed in current sources (and
back-patched so it will be in 7.0.3).

In the long run it'd be nice if the backend either handled this sort
of query correctly or at least raised an error, but that's probably
not going to happen for 7.1. We'll need some way of declaring in the
datatype system what kind of data the outputs of output-conversion
functions really are. Various people (including me) have muttered
about this off-and-on, but no one's put forward a complete proposal.

regards, tom lane

In response to

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Patrick Welche 2000-10-02 17:45:08 Re: PsqlODBC broken due to int4out(usesysid)
Previous Message Patrick Welche 2000-10-02 15:36:02 PsqlODBC broken due to int4out(usesysid)