From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ludek Finstrle <luf@pzkagis.cz>
Cc: pgsql-interfaces@postgresql.org
Cc: pgsql-odbc@postgresql.org
Subject: Re: [ODBC] BLOB handling compatibility with PostgreSQL > 7.4
Date: Tue, 06 Dec 2005 14:07:13 -0500
Message-ID: <15186.1133896033@sss.pgh.pa.us> (raw)
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>
Ludek Finstrle <luf@pzkagis.cz> 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
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, luf@pzkagis.cz, pgsql-odbc@postgresql.org
Subject: Re: [ODBC] BLOB handling compatibility with PostgreSQL > 7.4
In-Reply-To: <15186.1133896033@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