Re: Trigger problem

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: miker(at)purplefrog(dot)com
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Trigger problem
Date: 2004-06-10 01:44:36
Message-ID: 40C7BD04.1040105@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On 6/8/2004 2:57 PM, Mike Rylander wrote:

> kasper wrote:
>
>> Hi guys
>>
>> Im tryint to make a trigger that marks a tuble as changed whenever someone
>> has updated it
>>
>> my table looks something like this
>>
>> create table myTable (
>> ...
>> changed boolean;
>> )
>>
>> now ive been working on a trigger and a sp that looks like this, but it
>> doesnt work...
>>
>> create function myFunction returns trigger as '
>> begin
>> new.changed = true;
>
> The line above is using the SQL equaliy opperator, you want the assignment
> operator:
>
> :=
>
> as in
>
> new.changed := true;

PL/pgSQL accepts both. What's wrong is that it's an AFTER trigger, which
is fired AFTER the new row is already stored on disk and thus cannot
change it any more.

Jan

>
>> return new;
>> end;
>> ' language 'plpgsql';
>>
>> create trigger myTrigger
>> after update on lektioner
>> for each row
>> execute procedure myFunction();
>>
>>
>> the code compiles, runs, and doesnt whine about anything, but nothing
>> changes...
>>
>> any ideas??
>>
>> - Kasper
>
> -miker
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2004-06-10 04:21:01 Re: Schema + User-Defined Data Type Indexing problems...
Previous Message Stephan Szabo 2004-06-09 20:30:30 Re: Trigger problem