| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | <gilberto(dot)castillo(at)etecsa(dot)cu>,<Maria(dot)L(dot)Wilson-1(at)nasa(dot)gov> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: constraint triggers |
| Date: | 2011-09-28 14:43:38 |
| Message-ID: | 4E82EC4A020000250004183A@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Gilberto Castillo Martínez<gilberto(dot)castillo(at)etecsa(dot)cu> wrote:
>> CREATE OR REPLACE FUNCTION increment_dataset_granule_count()
>> RETURN NULL;
> Replace RETURN NULL for RETURN NEW
That won't matter for an AFTER trigger:
http://www.postgresql.org/docs/9.0/interactive/trigger-definition.html
says:
| The return value is ignored for row-level triggers fired after an
| operation, and so they can return NULL.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kasia Tuszynska | 2011-09-28 18:01:57 | Re: Postgres 9 on 64 bit |
| Previous Message | Gilberto Castillo Martínez | 2011-09-28 14:26:29 | Re: constraint triggers |