Postgres avoid Trigger on delete cascade

Question

Hello i have a problem with a Trigger

i have 2 tables:

t_mandant
t_user_has_mandant

when i delete a row in t_user_has_mandant i call a trigger beforeDeleteUserMandant() but i need a possibility to ignore the trigger call when i delete a mandant from t_mandant

because t_user_has_mandant has a foreign key on t_mandant which is on delete cascade.

im using postgres 8.4

So, you want to change the logic of a trigger on t_user_has_mandant if the delete was caused by CASCADE FK from t_mandant? — Ihor Romanchenko
– Ihor Romanchenko, Commented May 21, 2013 at 13:31
@SerYoga, did you ever find a good solution to this problem? — kcstricks
– kcstricks, Commented Jun 7, 2020 at 23:01

Ihor Romanchenko · Accepted Answer · 2013-05-21 13:42:39Z

1

Read this page of the manual.

Using the variable

TG_TABLE_NAME

Data type name; the name of the table that caused the trigger invocation.

You can determine if the DELETE was from t_user_has_mandant or t_mandant.

answered May 21, 2013 at 13:42

Ihor Romanchenko

29k9 gold badges56 silver badges45 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Ser Yoga Over a year ago

i tried it: RAISE NOTICE 'table_name: %', TG_TABLE_NAME; the result was NOTICE: table_name: t_user_has_mandant but my sql query was delete from t_mandant where id_mandant = 555 ...

Ihor Romanchenko Over a year ago

Hm. Maybe. I havent tested my ansver.

Ihor Romanchenko Over a year ago

The other (but a bit ugly) way is to query pg_stat_activity view to get the text of current query and search for table names in it.

Ser Yoga Over a year ago

i think its to overelaborate :(

Collectives™ on Stack Overflow

Postgres avoid Trigger on delete cascade

1 Answer 1

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related