X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id CA12A9DCD1D; Tue, 6 Dec 2005 15:07:15 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 63787-10; Tue, 6 Dec 2005 15:07:15 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 867359DCBEC; Tue, 6 Dec 2005 15:07:13 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id jB6J7EIl015187; Tue, 6 Dec 2005 14:07:14 -0500 (EST) To: Ludek Finstrle cc: pgsql-interfaces@postgresql.org, pgsql-odbc@postgresql.org Subject: Re: [ODBC] BLOB handling compatibility with PostgreSQL > 7.4 In-reply-to: <20051206184402.GA24475@soptik.pzkagis.cz> References: <438B792D.6030802@bnl.gov> <20051205212806.GA17690@soptik.pzkagis.cz> <20051206142811.GA23334@soptik.pzkagis.cz> <259.1133881501@sss.pgh.pa.us> <20051206184402.GA24475@soptik.pzkagis.cz> Comments: In-reply-to Ludek Finstrle message dated "Tue, 06 Dec 2005 19:44:02 +0100" Date: Tue, 06 Dec 2005 14:07:13 -0500 Message-ID: <15186.1133896033@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.002 required=5 tests=[AWL=0.002] X-Spam-Score: 0.002 X-Spam-Level: X-Archive-Number: 200512/9 X-Sequence-Number: 5877 Ludek Finstrle writes: > I don't want to reinvent the wheel. Why do you feel a need to distinguish the domain from its underlying type on the client side? They're the same as regards representation and so on. The reason for the backend change was that client-side drivers (such as JDBC and ODBC) want to know the underlying datatype so that they know what representation to use etc. Distinguishing domains made their job harder not easier. If you want an add-on datatype that is really different from OID, then make a real datatype (CREATE TYPE). You can still piggyback on OID as the representation type --- steal its I/O functions and so on. regards, tom lane