From: Ludek Finstrle <luf@pzkagis.cz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-interfaces@postgresql.org
Cc: pgsql-odbc@postgresql.org
Subject: Re: [ODBC] BLOB handling compatibility with PostgreSQL > 7.4
Date: Tue, 6 Dec 2005 20:27:49 +0100
Message-ID: <20051206192749.GA24711@soptik.pzkagis.cz> (raw)
In-Reply-To: <15186.1133896033@sss.pgh.pa.us>
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>
<15186.1133896033@sss.pgh.pa.us>
> > 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.
I need to determine wheter to use lo_import for large objects.
There is implementation in ODBC used type named "lo" (comapring type
oid). Type oid doesn't represent only large objects.
> what representation to use etc. Distinguishing domains made their job
> harder not easier.
I agree with you except lo implementation in ODBC ;-)
> 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.
Does it cover lo_export which need oid as second parameter?
I'm sorry I'm new in using large objects and creating new types.
Thanks a lot
Luf
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: luf@pzkagis.cz, tgl@sss.pgh.pa.us, pgsql-odbc@postgresql.org
Subject: Re: [ODBC] BLOB handling compatibility with PostgreSQL > 7.4
In-Reply-To: <20051206192749.GA24711@soptik.pzkagis.cz>
* 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