| From: | Ken Been <kbbeen(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Melvin Davidson <melvin6925(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: interperting type oid in C code |
| Date: | 2015-10-19 19:50:37 |
| Message-ID: | CANe84ryxstACxng+XkA1N=T9bDiyECw+iniKukt6gA0RsmxjPg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Well, it's a few types, but the logic is different for each one, so they
have to be handled independently anyway.
On Mon, Oct 19, 2015 at 7:40 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
wrote:
> Ken Been wrote:
> > Those are more complicated, and it's not obvious to me how to use them.
> I
> > really think that all I need is something as simple as "if (my_oid ==
> > INT4OID) {...}". Is there any reason why I shouldn't just do that?
>
> I don't know. I was thinking that you might want to handle a larger set
> of type OIDs.
>
> --
> Álvaro Herrera http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2015-10-19 21:18:09 | Re: Are there any major benefits to using point and not real data type |
| Previous Message | Alvaro Herrera | 2015-10-19 19:40:40 | Re: interperting type oid in C code |