Re: For each statement trigger and update table

Oh, so you're defining transition relations (REFERENCING NEW TABLE, OLD
TABLE ) as in here?

CREATE TRIGGER paired_items_update
AFTER UPDATE ON paired_items
REFERENCING NEW TABLE AS newtab OLD TABLE AS oldtab
FOR EACH ROW
EXECUTE FUNCTION check_matching_pairs();

On Fri, Jan 3, 2020 at 5:55 PM Mike Martin <mike(at)redtux(dot)plus(dot)com> wrote:

> According to the docs, not possible to use a transition table and column
> list together
>
> On Fri, 3 Jan 2020, 23:39 Rene Romero Benavides, <rene(dot)romero(dot)b(at)gmail(dot)com>
> wrote:
>
>> > I can give code when I get home, but it's pretty simple stuff
>> please do so, along with your trigger definition. Are you aware that you
>> can define your update trigger to fire on a specific column?
>>
>> https://www.postgresql.org/docs/current/sql-createtrigger.html
>>
>> For UPDATE events, it is possible to specify a list of columns using
>> this syntax:
>>
>> UPDATE OF column_name1 [, column_name2 ... ]
>>
>>
>>
>> On Fri, Jan 3, 2020 at 5:21 PM Mike Martin <mike(at)redtux(dot)plus(dot)com> wrote:
>>
>>> Not sure if this is possible
>>> Basically I want to have a trigger which updates an array column in the
>>> same table when a column is updated
>>> This works as a row level trigger, but not as per statement
>>> I have hit the recursive issue (where update fires update trigger which
>>> fires etc)
>>> According to the docs I cannot use columns and relative tables together
>>>
>>> So any suggestions? I can give code when I get home, but it's pretty
>>> simple stuff
>>>
>>
>>
>> --
>> El genio es 1% inspiración y 99% transpiración.
>> Thomas Alva Edison
>> http://pglearn.blogspot.mx/
>>
>>

--
El genio es 1% inspiración y 99% transpiración.
Thomas Alva Edison
http://pglearn.blogspot.mx/