On Mon, Apr 08, 2002 at 01:03:41PM -0400, Tom Lane wrote:
> The search_path case is the main reason why I'm intent on changing
> the behavior of SET; without that, I'd just leave well enough alone.
Is there more variables like "search_path"? If not, I unsure if one
item is good consideration for change others things.
> Possibly some will suggest that search_path shouldn't be a SET variable
> because it needs to be able to be rolled back on error. But what else
> should it be? It's definitely per-session status, not persistent
It's good point. Why not make it more transparent? You want
encapsulate it to standard and current SET statement, but if it's
something different why not use for it different statement?
SET SESSION search_path TO 'something';
(...or something other)
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
