Re: [HACKERS] IF (NOT) EXISTS in psql-completion
От | Michael Paquier |
---|---|
Тема | Re: [HACKERS] IF (NOT) EXISTS in psql-completion |
Дата | |
Msg-id | CAB7nPqQ-FaDP6GdfAeNOdYMGNgohD7rEf6R92QyUyC0y+cOQ3A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] IF (NOT) EXISTS in psql-completion (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [HACKERS] IF (NOT) EXISTS in psql-completion
|
Список | pgsql-hackers |
On Mon, Feb 27, 2017 at 10:12 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Michael Paquier <michael.paquier@gmail.com> writes: >> On Mon, Feb 27, 2017 at 5:21 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >>> So I'd be a whole lot happier if it didn't do that. Can we really not >>> add the desired features in a more localized fashion? > >> As "if not exists" is defined after the object type if would not be >> that complicated to add completion for IE/INE after the object type >> with a set of THING_* flags in words_after_create. One missing piece >> would be to add completion for the objects themselves after IE or INE >> have been entered by the user, but I would think that tweaking the >> checks on words_after_create[i] would be doable as well. And that >> would be localized. > > BTW ... can anyone explain to me the reason why we offer to complete > CREATE OBJECT with the names of existing objects of that kind? > That seems pretty darn stupid. I can see offering the names of existing > schemas there, if the object type is one that has schema-qualified names, > but completing with an existing object name is just setting up to fail > isn't it? Isn't that to facilitate commands appended after CREATE SCHEMA? Say table foo is in schema1, and creating it in schema2 gets easier with tab completion? -- Michael
В списке pgsql-hackers по дате отправления: