FWD » Core Development » Database

• runtime support for TRIGGER PROCEDURE (DELETE, WRITE, CREATE), DISABLE TRIGGERS, ON FIND OF table;
• need report changes to check if there are other ON statement cases in customer code, but it is likely that other ON statement usage is at least small in nature (and it would only be for DELETE, WRITE or CREATE, so the functionality must already be there);
• there will need to be work on the conversion side to emit procedures/trigger blocks (for ON statement) and register them.

What needs to be done:

1. Allow registration for WRITE and FIND schema triggers.
2. Fire WRITE and FIND triggers at proper places.
3. Handle triggers as arbitrary classes or DatabaseTrigger instances instead of classes that implement AssignTrigger/DeleteTrigger/etc. interface.
4. Implement execution of session and schema triggers (i.e. call TriggerClass.create/write/etc.).
5. Implement scoped registerDatabaseTrigger (with optional OVERRIDE) and deregisterDatabaseTrigger.
6. Make sure that triggers are properly handled as top level blocks.
7. Implement scoped disable*Triggers.

My estimates:

1. 3 h - Allow registration for WRITE and FIND schema triggers.
2. 16 h, need to find these proper places and check all cases - Fire WRITE and FIND triggers at proper places.
3. 6 h - Handle triggers as arbitrary classes or DatabaseTrigger instances instead of classes that implement AssignTrigger/DeleteTrigger/etc. interface.
4. 6 h - Implement execution of session and schema triggers (i.e. call TriggerClass.create/write/etc.).
5. 16 h - Implement scoped registerDatabaseTrigger (with optional OVERRIDE) and deregisterDatabaseTrigger.
6. If everything is works as expected - 4 h - Make sure that triggers are properly handled as top level blocks.
7. 6 h - Implement scoped disable*Triggers.