Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Moreover, the unset state shouldn't exist at all. No parameter can behave
> reasonably if unset behaved differently from an empty string. Explicitly
> assigning an unset state doesn't work. So it seems that for all external
> communication, an un
Peter Eisentraut wrote:
The function current_setting returns 'unset' if a parameter is not
set.
This is not documented,
It is documented to produce equivalent output as the sql SHOW command.
Although the reference page for SHOW does not specifically address
parameters that are not set, it
Am Dienstag, 10. Januar 2006 16:01 schrieb Tom Lane:
> That's because SHOW does the same thing. SHOW has a little problem in
> that it can't readily show the difference between "null" and an empty
> string, so while I find the behavior pretty ugly, I don't have a better
> idea.
Since SHOW is prim
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> The function current_setting returns 'unset' if a parameter is not set.
> Should it not return null? This is not documented, so I guess this just
> arose out of the implementation, or is this intentional?
That's because SHOW does the same thing.
The function current_setting returns 'unset' if a parameter is not set.
Should it not return null? This is not documented, so I guess this just
arose out of the implementation, or is this intentional?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(en
