From: | Rod Taylor <rbt(at)rbt(dot)ca> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: View definition formatting |
Date: | 2003-04-01 20:21:20 |
Message-ID: | 1049228479.35327.110.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers pgsql-hackers |
On Tue, 2003-04-01 at 14:18, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Perhaps as a workaround you could invent a standard indentation format and
> > format the rules automatically that way, so that users will be able to
> > find everything in the same place automatically after the second edit
> > cycle.
>
> Perhaps we could make pg_get_ruledef and friends try to prettyprint
> their output a little better, instead of duplicating such logic in
> various clients (which couldn't do nearly as well at it anyway without
> re-parsing the string :-().
>
> Does anyone have code that depends on these functions returning
> single-line output? (I suppose the pg_rules and pg_views views might
> get a bit ugly, but perhaps psql could be taught to format data with
> embedded newlines better than it does now...)
I do -- but the only thing it does is format the output to look better.
--
Rod Taylor <rbt(at)rbt(dot)ca>
PGP Key: http://www.rbt.ca/rbtpub.asc
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2003-04-01 21:47:04 | Re: pgadmin3: present and future |
Previous Message | Tom Lane | 2003-04-01 19:58:52 | Re: View definition formatting |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-04-01 20:24:34 | Re: mariposa |
Previous Message | Moritz Sinn | 2003-04-01 20:06:36 | mariposa |