From: | Greg <grigorey(at)yahoo(dot)co(dot)uk> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Data type OIDs |
Date: | 2010-07-07 18:13:16 |
Message-ID: | 361426.20952.qm@web24303.mail.ird.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Cool. Thanks Joe! Thats exactly what I needed to know.
--- On Wed, 7/7/10, Joe Conway <mail(at)joeconway(dot)com> wrote:
From: Joe Conway <mail(at)joeconway(dot)com>
Subject: Re: [NOVICE] Data type OIDs
To: "Greg" <grigorey(at)yahoo(dot)co(dot)uk>
Cc: "Thom Brown" <thombrown(at)gmail(dot)com>, pgsql-novice(at)postgresql(dot)org
Date: Wednesday, 7 July, 2010, 17:44
On 07/07/2010 01:15 AM, Greg wrote:
> Hi Thom, well, it relates to reading/writing data using PostgreSQL
> protocol (v3). For example RowDescription message uses type OID to
> identify data type of the field. Same as with Parse message I need to
> specify OID of the parameter data type. As a result I want to declare an
> enum of all used data types and assignd PostgreSQL data type OID to
> appropriate value - so development could be a little more intuitive.
I don't think there is any promise that type OIDs will never change, but
in practice they have been stable for many releases over 10+ years.
You should, however, use the macros in pg_type.h to refer to them, e.g.
INT8OID, TEXTOID, etc.
HTH,
Joe
--
Joe Conway
credativ LLC: http://www.credativ.us
Linux, PostgreSQL, and general Open Source
Training, Service, Consulting, & Support
From | Date | Subject | |
---|---|---|---|
Next Message | John T. Dow | 2010-07-07 19:11:44 | Re: Dropped table, no backup, restore from file system backup or WAL files? |
Previous Message | Arvind Sharma | 2010-07-07 17:06:17 | Triggers, Stored Procedures to Aggregate table ? |