From: | darcy(at)druid(dot)net (D'Arcy J(dot)M(dot) Cain) |
---|---|
To: | maillist(at)candle(dot)pha(dot)pa(dot)us (Bruce Momjian) |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] INT2OID, etc. |
Date: | 1998-02-27 12:54:32 |
Message-ID: | m0y8PJB-00000oC@druid.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thus spake Bruce Momjian
> I will say that pg_dump does use it, but it is not really a 3rd party
> library.
Maybe everything in src/interfaces should be considered the same way.
> I recommend you use the file, and make them supply the pgsql source
> directory as part of the compile, that way, you can access the files you
> need directly. You can do a lookup in pg_type for the names of the
> types you want. Maybe you can even write a little psql script to
> extract the oid's you need from pg_type, convert the output to #defines,
> and #include that in your compile.
That's a thought. I just pulled the defines I needed out with many
comments about what a bad boy I was for doing that. I'll look at
something like that.
--
D'Arcy J.M. Cain <darcy(at){druid|vex}.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 424 2871 (DoD#0082) (eNTP) | what's for dinner.
From | Date | Subject | |
---|---|---|---|
Next Message | D'Arcy J.M. Cain | 1998-02-27 13:05:23 | Re: [HACKERS] INT2OID, etc. |
Previous Message | Michael Meskes | 1998-02-27 11:13:29 | Re: [HACKERS] common area |