Re: [GENERAL] Delete trigger and data integrity

2014-05-27 Thread Alban Hertroys
On 27 May 2014 12:25, Yvonne Zannoun wrote: > CREATE OR REPLACE FUNCTION delete_records() > RETURNS TRIGGER AS $$ > BEGIN > delete from "TABLE"; > RETURN NEW; > END; > $$ > LANGUAGE plpgsql; You can't return NEW in an ON DELETE trigger - there is no NEW record. Since you're going with a STATE

Re: [GENERAL] Delete trigger and data integrity

2014-05-27 Thread Yvonne Zannoun
Thank you very much, that answers my question. And yes, I think you are right with the FOR EACH ROW/STATEMENT, I didn't think that through for this example. Thank you for your help! Kind regards, *Yvonne Zannoun* Graduate Technical Consultant Snowflake Software *Tel: +44 (0) 23 80238 232* Emai

Re: [GENERAL] Delete trigger and data integrity

2014-05-27 Thread Albe Laurenz
Yvonne Zannoun wrote: > I have this question regarding delete triggers and how it affects data > integrity. > So here goes: I have this trigger which deletes everything before I insert > new rows. > > CREATE OR REPLACE FUNCTION delete_records() > RETURNS TRIGGER AS $$ > BEGIN > delete from "

[GENERAL] Delete trigger and data integrity

2014-05-27 Thread Yvonne Zannoun
Hello everyone, I have this question regarding delete triggers and how it affects data integrity. So here goes: I have this trigger which deletes everything before I insert new rows. CREATE OR REPLACE FUNCTION delete_records() RETURNS TRIGGER AS $$ BEGIN delete from "TABLE"; RETU