From: | Andreas Kretschmer <akretschmer(at)spamfence(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PL/SQL & unset custom variable |
Date: | 2009-09-02 14:39:29 |
Message-ID: | 20090902143929.GA6774@tux |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Gordon Ross <gr306(at)ucs(dot)cam(dot)ac(dot)uk> wrote:
> (I'm using Postgres 8.3)
>
> I have a trigger that references a custom variable. Most of the time this
> custom variable is set, and I have no problems.
>
> However, in certain corner cases the custom variable is not set and the
> trigger fails.
>
> Is there a way to either test if the custom variable is set, or to specify a
> global default for the custom variable ?
I think, you can use COALESCE(your_variable, default_value) to solve
that problem. Try it, it is untested.
Andreas
--
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect. (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly." (unknown)
Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889°
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-09-02 14:41:56 | Re: Ungooglable error message when running initdb: Symbol not found: _check_encoding_conversion_args |
Previous Message | Merlin Moncure | 2009-09-02 14:31:27 | Re: creating array of integer[] out of query - how? |