QuickSQL should generate compound triggers by default about quicksql HOT 2 OPEN

Could you please provide an example where more than one trigger is generated for the same table? In current JS implementation trigger functionality is aggregated under table_name_bui, e.g.

dept /rowversion
    name /lower

which generates

-- create tables

create table dept (
    id             number generated by default on null as identity
                   constraint dept_id_pk primary key,
    name           varchar2(255 char),
    row_version    integer not null
);

-- triggers
create or replace trigger dept_biu
    before insert or update
    on dept
    for each row
begin
    :new.name := lower(:new.name);
    if inserting then
        :new.row_version := 1;
    elsif updating then
        :new.row_version := NVL(:old.row_version, 0) + 1;
    end if;
end dept_biu;
/

-- Generated by Quick SQL...

from quicksql.

Vadim,

Yes, the current implementation creates a single trigger. But the trigger that it creates is a ‘classic trigger’ rather than a compound trigger. The name of the trigger has an _biu at the end. This would encourage anyone who wanted logic to after after insert or update to create a second _aiu trigger. What I’m suggesting is we encourage the better behavior of a single trigger for each table, as a compound trigger, with the ‘extra’ spots commented out.

Does that make sense? I tried to communicate that previously, I’m sorry it wasn’t clear.

from quicksql.