From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: psql tab-complete and backslash patch |
Date: | 2005-08-15 07:50:57 |
Message-ID: | 43004961.9090402@kaltenbrunner.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Tom Lane wrote:
> Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
>
>>attached is a patch against psql that makes psql's tabcomplete code
>>ROLES aware, adds SET SCHEMA and basic CREATE DATABASE/TRIGGER support
>>as well as some other minor things.
>
>
> Applied with some changes. I didn't see the point of making \du
> backwards compatible to older versions; we've never worried about that
> before in psql's \d commands. Also I thought the "Attributes" approach
> of the old \du code was well past its usefulness, so I just changed it
> to separate columns.
thanks for applying!
While I know that we have never guaranteed backwards-compatibility for
psql's backslash commands (or for tab-complete either) I modeled this
after the \db-tablespace code. Removing it altogether is fine too :-)
Any particular reason why you dropped the SET SCHEMA <tab> part of my
patch ?
Stefan
From | Date | Subject | |
---|---|---|---|
Next Message | Abhijit Menon-Sen | 2005-08-15 08:29:06 | Re: Command args user password |
Previous Message | NosyMan | 2005-08-15 07:09:39 | Command args user password |