Subject: Re: IF (NOT) EXISTS in psql-completion
To: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>,
 pgsql-hackers@postgresql.org
References: <20160205.170901.60679714.horiguchi.kyotaro@lab.ntt.co.jp>
From: Peter Eisentraut <peter_e@gmx.net>
Message-ID: <56E8C077.2000903@gmx.net>
Date: Tue, 15 Mar 2016 22:09:59 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0)
 Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <20160205.170901.60679714.horiguchi.kyotaro@lab.ntt.co.jp>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On 2/5/16 3:09 AM, Kyotaro HORIGUCHI wrote:
> I considered how to make tab-completion robust for syntactical
> noises, in other words, optional words in syntax. Typically "IF
> (NOT) EXISTS", UNIQUE and TEMPORARY are words that don't affect
> further completion.

To repeat the question I raised in the previous commit fest about tab
completion: Why do you want tab completion for IF NOT EXISTS?  When you
tab complete, the completion mechanism will show you whether the item in
question exists.  What is the use case?


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers