Is it safe to use fundamental type OIDs defined in server/catalog/pg_type.h from client?
"Hoon H." <[email protected]> Fri, 6 Dec 2013 05:43:13 +0900
| Newsgroups | gmane.comp.db.postgresql.interfaces |
|---|---|
| Message-ID | <[email protected]> |
Hello folks. I am writing a C/C++ program which uses `libpq`. I am stuck at getting result from PQresult because I want to parse text from result automatically by its type OID value. But it's unclear how I should handle type informations. What I need is only fundamental built-in types - boolean, int, float, text, timestamp, binary. Maybe adding some system required system - such as OID type itself. The problem is OID constant values for built-in types are not defined in client-side. According to some mailing list entries, http://www.postgresql.org/message-id/[email protected] http://www.postgresql.org/message-id/[email protected] It seems safe to use macros defined in `server/catalog/pg_type.h`, but I still doubt because I couldn't find any official policy on these values. Though I agree people on the mailing list entries, but still this is completely up to dev-team's decision. Can I ask some official policy on these values - OID values for built-in types? If there's some publicly existing policy, please drop me some link. It's too hard to find it. -- Sent via pgsql-interfaces mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-interfaces