Josh Kupershmidt writes:
> Hrm, guess I learned something. I tested with a trigger function which used:
> ...
> IF NEW IS NULL THEN
>RAISE NOTICE 'new is null.';
> ...
> which was giving me 'ERROR: record "new" is not assigned yet' when
> used as an on-delete trigger.
Hmm ... I won
On Thu, May 5, 2011 at 10:36 PM, Tom Lane wrote:
> That is, in fact, exactly the behavior you get if you declare a RECORD
> variable and set it to NULL. If these variables were indeed not
> declared, you'd get a complaint about "new" not being a known variable.
Hrm, guess I learned something. I
Josh Kupershmidt writes:
> [Moving to -docs]
> On Mon, May 2, 2011 at 12:00 PM, Pavel Stehule
> wrote:
>> It isn't correct. NEW is not declared in DELETE trigger, OLD isn't
>> declared in INSERT
That claim is flat out wrong.
> If I've understood you correctly, the problem is that the docs clai
[Moving to -docs]
On Mon, May 2, 2011 at 12:00 PM, Pavel Stehule wrote:
> Hello
>
> one czech user reported a bug in documentation -
> http://www.postgresql.org/docs/8.4/static/plpgsql-trigger.html
>
> NEW
>
> Data type RECORD; variable holding the new database row for
> INSERT/UPDATE operatio
Susanne Ebrecht wrote:
> Hello,
>
> During translating start.sgml - I found a sentence where I am not sure
> if it is correct.
>
> tutorial-createdb.html
>
> Second paragraph below the "permission denied to create a database"
> error message there is
> the sentence:
>
> " You can also create d
The documentation for ON_ERROR_STOP states, or at least implies by
omission, that it only affects the behavior in non-interactive scripts:
By default, if non-interactive scripts encounter an error, such
as a malformed SQL command or internal meta-command, processing
continu
