Re: What's the CURRENT schema ?
От | Hiroshi Inoue |
---|---|
Тема | Re: What's the CURRENT schema ? |
Дата | |
Msg-id | EKEJJICOHDIEMGPNIFIJEEGKHGAA.Inoue@tpf.co.jp обсуждение исходный текст |
Ответ на | Re: What's the CURRENT schema ? (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
> -----Original Message----- > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > > Fernando Nasser <fnasser@redhat.com> writes: > > Christopher Kings-Lynne wrote: > >> You know, I'm kinda surprised that the spec doesn't define a > CURRENT_SCHEMA > >> variable you can query??? > > > Maybe because it would be the same as CURRENT_USER. > > It'd probably make sense for us to have one, though, given that I'm > intent on not hardwiring the two concepts together as the spec does ;-). > Although you can interrogate the search path with SHOW, that's not very > accessible at the SQL level, so an SQL function seems useful too. > > I'd be inclined to make CURRENT_SCHEMA return the name of the schema > that is the default creation target namespace (viz, the front of the > search path). Thoughts? I think only one schema other than TEMP or catalog is allowed in the search path for the resolution of table name. I can call the schema the CURRENT_SCHEMA. If the restricted search path is inappropriate for the resolution of function, type etc name, you have to provide another path IMHO. BTW every time I examined SQL99, I can find neither the description CURRENT_SCHEMA == CURRENT_USER nor the one that the schema name of an unqualified table name may vary according to the table name. Probably it's because of my poor English. I'm happy if you could tell me where to find it. regards, Hiroshi Inoue
В списке pgsql-hackers по дате отправления: