Re: PsqlODBC broken due to int4out(usesysid)

Patrick Welche <prlw1@newn.cam.ac.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