"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
> Still, would it make more sense for SHOW search_path
> to return this:
> "$user",public
Can't get excited about it. SHOW is meant for human consumption,
not programs ...
regards, tom lane
---(end
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Well, sure, because you told it to. Why isn't the last parameter "false"?
Thanks. I knew I was overlooking something. I've obviously been staring at
the code too long. :) Still, would it make more sense for SHOW search_path
to return this:
"$use
"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
> This works fine:
> SELECT set_config('search_path', '$schema,' ||
> current_setting('search_path'), true);
> ...but does not last outside of a transaction.
Well, sure, because you told it to. Why isn't the last parameter
"false"?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm trying to figure out a way to modify the search_path temporarily, but
the "$user" construct is making this difficult. I need to prepend a schema
to the path. This works fine:
SELECT set_config('search_path', '$schema,' || current_setting('search
