Re: Schema variables - new implementation for Postgres 15
| От | Wolfgang Walther |
|---|---|
| Тема | Re: Schema variables - new implementation for Postgres 15 |
| Дата | |
| Msg-id | 93728f61-5510-4c7a-9d3f-502edf303d25@technowledgy.de обсуждение исходный текст |
| Ответ на | Re: Schema variables - new implementation for Postgres 15 (Pavel Stehule <pavel.stehule@gmail.com>) |
| Ответы |
Re: Schema variables - new implementation for Postgres 15
|
| Список | pgsql-hackers |
Pavel Stehule: > But in this case you could make variables and tables share the same > namespace, i.e. forbid creating a variable with the same name as an > already existing table. > > > It helps, but not on 100% - there is a search path I think we can ignore the search_path for this discussion. That's not a problem of variables vs tables, but just a search path related problem. It is exactly the same thing right now, when you create a new table x(x) in a schema which happens to be earlier in your search path. The objection to the proposed approach for variables was that it would introduce *new* ambiguities, which Alvaro's suggestion avoids. Best, Wolfgang
В списке pgsql-hackers по дате отправления: