Re: Tom Lane 2012-04-04 <28647.1333558...@sss.pgh.pa.us> > Now, Scott's comment seems to me to offer a principled way out of this: > if we define the intended semantics of search_path as being similar > to the traditional understanding of Unix PATH, then it's not an error > or even unexpected to have references to nonexistent schemas in there.
Btw, the default setting does already work like this: "$user",public. It is not an error for "$user" not to exist, but it is a very nice default because it will be used as soon as it appears. It would be logical to treat all other cases the same. I then could put the search_path into my .psqlrc and then have a "one size fits all" search path for all my databases, etc... > But as soon as you say "I want warnings in some cases", I think we have > a mess that nobody is ever going to be happy with, because there will > never be a clear and correct definition of which cases should get > warnings. As it looks impossible to divide the gray area, I'd opt to just drop the warning and accept all syntactically valid strings. Christoph -- c...@df7cb.de | http://www.df7cb.de/
signature.asc
Description: Digital signature
