| From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: psql backslash consistency |
| Date: | 2005-05-27 17:58:05 |
| Message-ID: | 1117216685.24459.2329.camel@camel |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Fri, 2005-05-27 at 03:45, Peter Eisentraut wrote:
> Tom Lane wrote:
> > Greg Sabino Mullane <greg(at)turnstep(dot)com> writes:
> > > Attached is my "backslash consistency" patch which basically makes
> > > all the backslash commands behave as \dt does: \d* shows non-system
> > > objects, and \d*S shows system objects.
> >
> > Could we have a way to turn this off? At least for functions and
> > operators? For my usage, at least, this will be a serious step
> > backwards in usefulness.
Do you have an implementation in mind? I'm having trouble coming up with
a way to do it cleanly.
>
> I see hardly any use case for showing only user-defined functions or
> types by default. I think consistency is not necessarily desirable
> here.
>
See the archives for previous discussion and/or use cases.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-05-27 18:02:33 | Re: psql backslash consistency |
| Previous Message | Bruce Momjian | 2005-05-27 15:18:11 | Re: entab vs. gcc4 again |