Peter Geoghegan on Twitter: "@shochdoerfer This is an AFTER trigger, you see. Those are generally used to modify other table. Only BEFORE triggers "intercept" UPDATEs." / Twitter

When executing an UPSERT in #PostgreSQL it seems "new" and "old" in my trigger hold the same value. Expected behaviour?

1

Replying to

INSERT or UPDATE trigger?

2

@shochdoerfer@phpc.social

@shochdoerfer

Oct 7, 2015

Replying to

@petervgeoghegan

can put up a gist if needed...

1

Replying to

Do.

1

@shochdoerfer@phpc.social

@shochdoerfer

Oct 7, 2015

Replying to

@petervgeoghegan

see here ht.ly/T8a6S - Quite likely my mistake, but can`t spot the error... :P

1

Peter Geoghegan

@petervgeoghegan

Replying to

@shochdoerfer

This is an AFTER trigger, you see. Those are generally used to modify other table. Only BEFORE triggers "intercept" UPDATEs.

5:51 PM · Oct 7, 2015Twitter Web Client

Replying to

Also, since it's AFTER trigger, "RETURN NEW" could be replaced with "RETURN NULL" without consequence -- return value ignored.

@shochdoerfer@phpc.social

@shochdoerfer

Oct 7, 2015

Replying to

@petervgeoghegan

right, thanks for pointing out. Makes sense now ;)

Conversation