Hi,
> Then I create a materialized view MV1 (which is actually a table) that is
> updated by triggers on table T1.
>
> Then I create a second second materialized view MV2.
> Again I update it with triggers on table T1.
> But this time it also reads MV1 for some generated values.
Could you not use one trigger for both MV1 and MV2?
> So if this would be easy it would be much appreciated :-)
I will add a feature request:
"
Triggers: support user defined execution order. Oracle:
CREATE OR REPLACE TRIGGER TRI_TEST_2 BEFORE INSERT
ON TEST FOR EACH ROW FOLLOWS TRI_TEST_1.
MS SQL Server: sp_settriggerorder.
SQL specifies that multiple triggers should be fired in
time-of-creation order.
PostgreSQL uses name order, which was judged to be more convenient.
Derby: triggers are fired in the order in which they were created.
"
Actually I like the PostgreSQL behavior. So far I don't know about
other databases.
Regards,
Thomas
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
