| From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Cc: | A B <gentosaker(at)gmail(dot)com> |
| Subject: | Re: Trigger problem, record "new" is not assigned yet |
| Date: | 2011-02-10 15:01:32 |
| Message-ID: | 201102100701.32715.adrian.klaver@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thursday, February 10, 2011 6:29:58 am A B wrote:
> Hello.
>
> I'm probably doing some very basic error here, but I get
>
> ERROR: record "new" is not assigned yet
> The tuple structure of a not-yet-assigned record is indeterminate.
>
> when I try this small example
>
> create table foo(x int);
>
> create or replace function trigger_foo() returns trigger language plpgsql
> as $$ declare v_i integer;
> begin
> select count(1) into v_i from foo;
> if new.x >18 then
> raise exception 'error';
> else
> return null;
> end if;
> end; $$;
>
> CREATE TRIGGER trigger_foo AFTER INSERT ON foo for each row EXECUTE
> PROCEDURE trigger_foo();
>
> insert into foo (x) values (15);
>
>
> And the table foo only have 14 lines right now.
>
> Can someone help me spot the error? :-)
The above works here, Postgres 9.0.3. Was that the complete error message? Is
there more than one foo across the schemas?
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vick Khera | 2011-02-10 15:03:03 | Re: Trigger problem, record "new" is not assigned yet |
| Previous Message | A B | 2011-02-10 14:38:09 | Re: Trigger problem, record "new" is not assigned yet |