The use case is that I need to transfer some information from one
table to other tables in aggregated form on the fly while the data
arrives. The logic of aggregation is mainly the same but depends on
destination table and also can vary with parameters. So now I need to
have at least one trigger class for each destination table instead of
heaving one parametrized. Also every time I need to change parameters
I need to recompile trigger in java and restart database instead of
using "drop trigger" and "create trigger". Though now its not the case
but may be in future I will also need to do this all (create
destination tables and triggers) at runtime with unpredictable
parameters.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
