| From: | darcy(at)druid(dot)net (D'Arcy J(dot)M(dot) Cain) |
|---|---|
| To: | vadim(at)sable(dot)krasnoyarsk(dot)su (Vadim B(dot) Mikheev) |
| Cc: | hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] INT2OID, etc. |
| Date: | 1998-02-27 13:05:23 |
| Message-ID: | m0y8PTf-00000oC@druid.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thus spake Vadim B. Mikheev
> On the one hand, client applications/interfaces shouldn't use
> server internal constants like these but query database to get
> type' name using type OIDs (like pg_dump does for \d-s).
>
> On the other hand - performance! And ability to use constants
> for built-in types is good thing.
>
> I like second way (and so - we should copy pg_type to ~pgsql/include or
> something like this) but it would be nice if you support more
> general 1st way too.
I think I'll write a program to extract this info and create a header
file. Perhaps that program can be dropped into the distribution.
The only problem is that it has to be run after the system has been
built, installed and initialized so it has to be run separately.
Still, it's better than reinventing it for every package that needs it.
--
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 | Tatsuo Ishii | 1998-02-27 13:30:13 | Re: [HACKERS] Current 6.3 issues |
| Previous Message | D'Arcy J.M. Cain | 1998-02-27 12:54:32 | Re: [HACKERS] INT2OID, etc. |