Thread: [HACKERS] Bogus tab completion tweak for UPDATE ... SET ... =

[HACKERS] Bogus tab completion tweak for UPDATE ... SET ... =

From
Thomas Munro
Date:
Hi,

Even though the following is coincidentally meaningful, I don't think
it was intentional or is useful:

postgres=# update foo set x = DEFAULT

Shouldn't that completion should be suppressed, like in the attached?

-- 
Thomas Munro
http://www.enterprisedb.com

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

Attachment

Re: [HACKERS] Bogus tab completion tweak for UPDATE ... SET ... =

From
Tom Lane
Date:
Thomas Munro <thomas.munro@enterprisedb.com> writes:
> Even though the following is coincidentally meaningful, I don't think
> it was intentional or is useful:

> postgres=# update foo set x = DEFAULT

Uh, seems perfectly sane to me.  Why should we assume that can't be
what the user wants?
        regards, tom lane