Message-ID: <4A2720DE.6070003@joeconway.com>
Date: Wed, 03 Jun 2009 18:18:22 -0700
From: Joe Conway <mail@joeconway.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.8.0.12) Gecko/20071019 Fedora/1.5.0.12-3.fc6 pango-text
	Thunderbird/1.5.0.12 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: Florian Weimer <fw@deneb.enyo.de>, pgsql-interfaces@postgresql.org
Subject: Re: Type OIDs
References: <877hztupfn.fsf@mid.deneb.enyo.de>
 <10172.1244057188@sss.pgh.pa.us>
In-Reply-To: <10172.1244057188@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Tom Lane wrote:
> Florian Weimer <fw@deneb.enyo.de> writes:
>> Can I embed the types I'm interested in into my program, or should I
>> query the server at least once per connection to get the mapping?  I'm
>> interested in types such as INTEGER, TEXT, BYTEA, etc.  No user
>> defined types, and nothing fancy.  Ultra-long-term portability isn't
>> required, either.
> 
> Well, the type OIDs of the standard built-in types haven't changed in
> at least ten years, but that doesn't mean we won't change 'em in the
> future.  I'd advise at least using the #define's from pg_type.h rather
> than writing actual numeric constants.

I'll second that. It's exactly what I've been doing in PL/R for several 
years now.

Joe