Hi Walter,
Hopefully, others will contribute a simpler solution on this topic; but, in my experience, sequences are totally independent of the tables, and should be modelled as such. For example, you can create a special package called "Sequences" in the package that contains your table's definition in your model. Since each table and it's corresponding sequence are independent from one another, there is nothing in Oracle that could directly tell a CASE tool that a sequence is tied to a table. (If you do model your seqs, I would suggest to create a <<dependency>> or a <<call>> relationship between each table and it's corresponding sequence in the diagram, so as to keep track of what seq belongs to what table.)
Please note that modelling sequences is not essential.
What can solve your code gen problem, however, is to include the CREATE SEQUENCE code together with (and just before) the trigger's code as one of the table's operations: create a new operation (say, tdb_cat_key), stereotype it as "trigger", copy or write your trigger's code into the operation's "Behaviour" tab, and have EA include both the CREATE SEQUENCE and CREATE TRIGGER code in the DDL:
CREATE SEQUENCE seq_cat
MINVALUE 0
START WITH 0
INCREMENT BY 1
NOCYCLE
NOCACHE
;
-- Won't work if it is not initialized
SELECT seq_cat.NEXTVAL
FROM dual;
-- Create the trig
CREATE OR REPLACE TRIGGER tdb_cat_key
BEFORE INSERT ON t_cat FOR EACH ROW
BEGIN
SELECT seq_cat.NEXTVAL INTO :new.cat_key FROM dual;
END tdb_cat_key;
/
When generating your DDL, and having selected the option to generate the trig, you will see this operation's code in the generated code. The seq and the trig will now be generated together with your table.
Hope it works for you as well as it has worked for me.
Jaime
