| From: | Michael Fuhr <mike(at)fuhr(dot)org> |
|---|---|
| To: | Marvin Bellamy <marvin(dot)bellamy(at)innovision(dot)com> |
| Cc: | "'pgsql-interfaces(at)postgresql(dot)org'" <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | Re: libpq and referencing data type OIDs |
| Date: | 2005-04-05 03:39:33 |
| Message-ID: | 20050405033933.GA21612@winnie.fuhr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
On Mon, Apr 04, 2005 at 03:58:12PM -0500, Marvin Bellamy wrote:
>
> I want to use postgres' datatype OID definitions and not use the literal
> Oid int values (I'm feeding them into PQexecParams()). But, it looks
> like these values are defined in a header not included by libpq-fe.h.
> When I try importing catalog/pg_type.h, I get a slew of missing data
> type errors. So, what's the appropriate way to reference OID data types?
Including postgres.h before catalog/pg_type.h should work. I'm not
sure how appropriate it is for clients to include backend headers,
but it's worked when I've done it.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marvin Bellamy | 2005-04-07 21:03:11 | What is the binary format for timestamps? |
| Previous Message | Tom Lane | 2005-04-05 01:43:18 | Re: Problems with PQfmod() returning -1 on varchar f |