From: Andro <andromede@gmail.com>
To: pgsql-interfaces@postgresql.org
Subject: Re: PQftype() and Oid
Date: Mon, 7 Aug 2006 09:34:34 +0200
Message-ID: <da7021e0608070034w5b40b060qf7c7b8b9094b9afa@mail.gmail.com> (raw)
In-Reply-To: <da7021e0608070033h55aa34dfi9ba4c941c44158fa@mail.gmail.com>
References: <da7021e0608040738l3b0880a1q5a76b838937f8c78@mail.gmail.com>
<20060805071426.GA1404@alamut.tdm.local>
<da7021e0608070033h55aa34dfi9ba4c941c44158fa@mail.gmail.com>
While I agree this is a reliable way of matching, this has a
significant impact on performance to make an extra query on each field
that I want the type of ! And this makes this approach definitly not
the one to implement IMO.
Best,
Charles
On 8/5/06, Volkan YAZICI <yazicivo@ttnet.net.tr> wrote:
> On Aug 04 04:38, Andro wrote:
> > Oids are in pg_type catalog (server side) and src/include/catalog/pg_type.h
> > (hard-wired).
> >
> > But what should we compare the Oid returned by PQftype() with?
> > Let's say I want to check if column 1 is a VARCHAR, do I have to
> >
> > if (PQftype(res,1) == 1043)
> > ...;
> >
> > ?
> > Isn't there a kind of enum which we could rely on to find out types? What if
> > Oids change in pg_type.h?
>
> You can make another query on pg_type to learn OID of a specific type.
> And then compare it with the returned one from PQftype(main_query_res).
>
> Furthermore, I think this is the only reliable way of accomplising this
> task. (IIRC, PHP PostgreSQL API does same too.) Otherwise, when you use
> hard-wired headers (e.g. by including pg_type.h) what will you do when
> related server has a custom type that isn't get shippied with the
> PostgreSQL headers you included.
>
>
> Regards.
>
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: andromede@gmail.com
Subject: Re: PQftype() and Oid
In-Reply-To: <da7021e0608070034w5b40b060qf7c7b8b9094b9afa@mail.gmail.com>
* 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