Bogus tab completion tweak for UPDATE ... SET ... =
Started by Thomas Munroabout 9 years ago2 messageshackers
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
Attachments:
fix-update-set-completion.patchapplication/octet-stream; name=fix-update-set-completion.patchDownload+2-1
Re: Bogus tab completion tweak for UPDATE ... SET ... =
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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers