| From: | eisentrp(at)csis(dot)gvsu(dot)edu |
|---|---|
| To: | Chris Bitmead <chris(at)bitmead(dot)com> |
| Cc: | Postgres Hackers List <hackers(at)postgreSQL(dot)org> |
| Subject: | Re: PQprint |
| Date: | 2000-07-03 14:33:56 |
| Message-ID: | Pine.LNX.4.21.0007031026480.8757-100000@eos04.csis.gvsu.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 4 Jul 2000, Chris Bitmead wrote:
> What was the reason that PQprint was abandoned and psql went in its own
> direction?
The printing routines had to be rewritten, in particular to make them more
modular. The options were to add a fourth(!) generation of printing
routines to libpq and live with them until the end of days, or make them
internal to psql and don't tell anyone when changes happen.
If you want to use psql's printing routines you can just use print.c with
no changes. I've made an effort to keep it independent of psql.
--
Peter Eisentraut Sernanders vaeg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Bitmead | 2000-07-03 14:38:38 | Re: Backend Question |
| Previous Message | Tom Lane | 2000-07-03 14:31:49 | Re: Backend Question |