From: Vick Khera [mailto:vivek@khera.org] Sent: Friday, June 28, 2013 9:35 AM To: David Greco Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] AFTER triggers and constraints
The last delete statement will throw a referential integrity error. In Oracle, same example, it does not as the trigger deletes the child.
Not sure your real case, but why not just make the FK on delete cascade and get rid of your trigger entirely?
Alternatively, what if you make your constratint initially deferred?
The actual use case is a bit different and complicated. When the constraint is initially deferred, it works as expected, and that is how I will work around the issue. But my point is, is this how it is SUPPOSED to work? It’s not clear to me yet that is the case. I would expect the statement to include the after row triggers (but not the after statement triggers).
