|
Home > Archive > PostgreSQL Interfaces > April 2005 > libpq and referencing data type OIDs
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
libpq and referencing data type OIDs
|
|
| Marvin Bellamy 2005-04-04, 8:04 pm |
| 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?
--
Marvin Keith Bellamy
Software Engineer
Innovision Corporation
913.438.3200
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql
.org so that your
message can get through to the mailing list cleanly
| |
| Michael Fuhr 2005-04-05, 7:02 am |
| 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/
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
|
|
|
|
|