From: Tom Lane <tgl@sss.pgh.pa.us>
To: prlw1@cam.ac.uk
Cc: pgsql-interfaces@postgresql.org
Subject: Re: PsqlODBC broken due to int4out(usesysid)
Date: Mon, 02 Oct 2000 13:10:47 -0400
Message-ID: <4979.970506647@sss.pgh.pa.us> (raw)
In-Reply-To: <20001002163602.H22505@quartz.newn.cam.ac.uk>
References: <20001002163602.H22505@quartz.newn.cam.ac.uk>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, prlw1@cam.ac.uk
Subject: Re: PsqlODBC broken due to int4out(usesysid)
In-Reply-To: <4979.970506647@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox