X-Original-To: pgsql-odbc@postgresql.org Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id B30DE474E4F for ; Fri, 21 Mar 2003 11:31:47 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.8/8.12.8) with ESMTP id h2LGVqub013533; Fri, 21 Mar 2003 11:31:52 -0500 (EST) To: Andreas Pflug Cc: pgsql-odbc@postgresql.org Subject: Re: using domain types with ODBC, esp. lo In-reply-to: <3E7B3BA7.20709@web.de> References: <3E7B3BA7.20709@web.de> Comments: In-reply-to Andreas Pflug message dated "Fri, 21 Mar 2003 17:19:51 +0100" Date: Fri, 21 Mar 2003 11:31:52 -0500 Message-ID: <13532.1048264312@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200303/44 X-Sequence-Number: 2763 Andreas Pflug writes: > The well-known data types PG_TYPE_DATETIME, PG_TYPE_TIMESTAMP_NO_TMZONE, > PG_TYPE_TIME, PT_TYPE_TIME_WITH_TMZONE are handled in a special way > concerning the atttypmod field. This will fail for domain types of that > base type. This is correct, since the domain won't expose the atttypmod it assigns to the underlying type. > Actually, best thing for this problems would be if the backend would > deliver the base type oid, not the user type oid. 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