X-Original-To: pgsql-odbc@postgresql.org
Received: from smtp.web.de (smtp03.web.de [217.72.192.158])
	by postgresql.org (Postfix) with ESMTP id 319D6475E9D
	for <pgsql-odbc@postgresql.org>; Fri, 21 Mar 2003 11:48:08 -0500 (EST)
Received: from p5081816a.dip0.t-ipconnect.de ([80.129.129.106] helo=web.de)
	by smtp.web.de with asmtp (TLSv1:RC4-MD5:128) (WEB.DE(Exim) 4.97 #53)
	id 18wPgi-0008KM-00
	for pgsql-odbc@postgresql.org; Fri, 21 Mar 2003 17:48:12 +0100
Message-ID: <3E7B4254.2080205@web.de>
Date: Fri, 21 Mar 2003 17:48:20 +0100
From: Andreas Pflug <Andreas.Pflug@web.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pgsql-odbc@postgresql.org
Subject: Re: using domain types with ODBC, esp. lo
References: <3E7B3BA7.20709@web.de> <13532.1048264312@sss.pgh.pa.us>
In-Reply-To: <13532.1048264312@sss.pgh.pa.us>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200303/46
X-Sequence-Number: 2765

>
>
>There was some discussion of that idea in pgsql-hackers last week, but
>we didn't come to a definite conclusion.  How do others feel about it?
>
>			regards, tom lane
>  
>
I think there a several ways:

- base type OID instead of user type OID. Might break some clients 
dealing with special types. ODBC users won't notice.
- a postgresql.conf option to tell the backend to use base type OID or 
user type OID. Would catch most cases.
- a connection specific setting to tell the backend to use base type OID 
or user type OID. For concurrent ODBC and weird clients use.
- base type additionally in the RowDescription message. Obviously, this 
would break the 7.3 protocol.

Regards,

Andreas