| From: | "Magnus Naeslund\(f\)" <mag(at)fbab(dot)net> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PQftype() |
| Date: | 2001-04-30 22:13:49 |
| Message-ID: | 03ae01c0d1c2$d56858e0$020a0a0a@totalmef |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
[snip]
>
> The system type OIDs are stable. User-defined types would probably have
> a new OID after a dump and reload.
>
> > Or could i do like the ODBC driver, autogenerate a .h out of that table.
>
> I would not recommend relying on compiled-in OID knowledge for any types
> other than the system-defined datatypes. If you expect to have to deal
> with user-defined types, it's best to cache the results of pg_type
> lookups at the client end. You need not worry about OIDs changing
> during a single client connection.
>
> regards, tom lane
>
Ok, then i can use static thing for my application (for now atleast).
Thanks..
Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Burton | 2001-04-30 22:17:44 | Re: COPY commands could use an enhancement. |
| Previous Message | Tom Lane | 2001-04-30 22:11:54 | Re: PQftype() |