"INSTEAD OF" trigger support for tables

[EPluribusUnum]

Hi *!

Currently only the view trigger has "routing" functionality.
E.g.: you can decide in the view trigger, that a delete actually is a soft delete - you execute an UPDATE not a DELETE.

The INSTEAD OF triggers should be executed before the other triggers.
In the INSTEAD OF trigger you should be able to signal, whether the the processing of the DML write operation should be continued or skipped to this record.

[mrotteveel]

You do that by using a view, and either forward the data to the table or do nothing.

[EPluribusUnum]

@mrotteveel : I can't just replace a table to a view in a huge legacy system.
(Currently you must find all DML execution on the table and do the routing logic everywhere because of the lack of centralized write.)

[aafemt]

I can't just replace a table to a view in a huge legacy system.
(Currently you must find all DML execution on the table and do the routing logic everywhere because of the lack of centralized write.)

You don't need that. Just create the view with exactly the same name as was the name of the table. Direct dependencies inside of the database are easy to find.

[EPluribusUnum]

@aafemt , you can't have a view and a table with the same name. I can't drop the table because of hundreds of dependencies. (And table rename still does not supported)