Comments on: Compound Triggers – Managing the Mutant Menace http://mikesmithers.wordpress.com/2010/04/24/compound-triggers-%e2%80%93-managing-the-mutant-menace/ Oracle - for when it was like that when you got there Sat, 25 May 2013 09:47:11 +0000 hourly 1 http://wordpress.com/ By: mikesmithers http://mikesmithers.wordpress.com/2010/04/24/compound-triggers-%e2%80%93-managing-the-mutant-menace/#comment-399 Thu, 27 May 2010 21:13:57 +0000 http://mikesmithers.wordpress.com/?p=417#comment-399 Joacquin,

It’s a good point.
I deliberately avoided using arrays to keep the example simple. Also, I can’t think of too many real-world situations where this would occur for a single Order.
Having checked however, it doesn’t work as expected if you use a PL/SQL table either.
The answer would appear to be to sort out the design. I’ll post on this again shortly.

Mike

Update : the new post is here

]]> By: Joaquin http://mikesmithers.wordpress.com/2010/04/24/compound-triggers-%e2%80%93-managing-the-mutant-menace/#comment-388 Mon, 24 May 2010 08:08:59 +0000 http://mikesmithers.wordpress.com/?p=417#comment-388 It does not work with multi-insert:

insert into misc_statuses SELECT ’1′, ‘ORDER’, ‘PACK’, sysdate, NULL FROM DUAL
UNION ALL SELECT ’1′, ‘ORDER’, ‘SEND’, sysdate, NULL FROM DUAL
UNION ALL SELECT ’2′, ‘ORDER’, ‘PACK’, sysdate, NULL FROM DUAL;

select * from misc_statuses;
KEY_VALUE DOMAIN_NAME STATUS START_DATE END_DATE
——— ———– —— ——————- ——–
1 ORDER PACK 24/05/2010 10:05:40
1 ORDER SEND 24/05/2010 10:05:40
2 ORDER PACK 24/05/2010 10:05:40

3 rows selected.

]]>