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

2017-03-13 Thread Tom Lane
Thomas Munro 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 l

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

2017-03-13 Thread Thomas Munro
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 fix-update-set-completion.patch D