Re: PQprint - Mailing list pgsql-hackers

From eisentrp@csis.gvsu.edu
Subject Re: PQprint
Date
Msg-id Pine.LNX.4.21.0007031026480.8757-100000@eos04.csis.gvsu.edu
Whole thread Raw
In response to PQprint  (Chris Bitmead <chris@bitmead.com>)
List 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@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden



pgsql-hackers by date:

Previous
From: eisentrp@csis.gvsu.edu
Date:
Subject: fcntl(F_SETLK)
Next
From: The Hermit Hacker
Date:
Subject: Re: Proposed new libpq API