| From: | nolan(at)celery(dot)tssi(dot)com |
|---|---|
| To: | gearond(at)cvc(dot)net |
| Cc: | mallah(at)trade-india(dot)com (Rajesh Kumar Mallah), peter_e(at)gmx(dot)net (Peter Eisentraut), pgsql-general(at)postgresql(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Subject: | Re: psql -et |
| Date: | 2003-07-24 16:08:00 |
| Message-ID: | 20030724160801.11379.qmail@celery.tssi.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
> A macro for the print, which substitutes:
>
> print()
> fflush()
>
> for a bare print is a good idea.
In addition to print(), fputs() is also used in several places.
Most of the \ commands appear to have their own formatting sections,
so changing them to use a macro or possibly a function would be desirable,
and a function would make separating terminal and \o output into
independent streams easier.
It may get even more complicated when considering laTex and HTML output.
As long as features are on the table, would there be any interest in
having an option to output in XML? (This may raise a number of XML
design questions, though, and I'm just starting to read 'XML in a Nutshell'.)
--
Mike Nolan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cory 'G' Watson | 2003-07-24 16:23:49 | Re: optimum postgres server configuration |
| Previous Message | Dennis Gearon | 2003-07-24 15:55:55 | Re: psql -e |