Received: from clio.trends.ca (root@clio.trends.ca [209.47.148.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e92HSOb05935 for ; Mon, 2 Oct 2000 13:28:24 -0400 (EDT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by clio.trends.ca (8.10.2/8.10.2) with ESMTP id e92HDDY28770 for ; Mon, 2 Oct 2000 13:13:13 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.0/8.11.0) with ESMTP id e92HAlB04982; Mon, 2 Oct 2000 13:10:47 -0400 (EDT) To: prlw1@cam.ac.uk cc: pgsql-interfaces@postgresql.org Subject: Re: PsqlODBC broken due to int4out(usesysid) In-reply-to: <20001002163602.H22505@quartz.newn.cam.ac.uk> References: <20001002163602.H22505@quartz.newn.cam.ac.uk> Comments: In-reply-to Patrick Welche message dated "Mon, 02 Oct 2000 16:36:02 +0100" Date: Mon, 02 Oct 2000 13:10:47 -0400 Message-ID: <4979.970506647@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200010/3 Patrick Welche 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