Hi, > I've thought about such approach with only the difference that in my > case parameters should be persistent, so should be stored in table..
Yes, you can do that as well. > Yes, this should work but maintaining this table is not very elegant > solution I think. To me, it sounds more secure than supporting Trigger constructors, and then re-create the triggers each time the parameters change. Reason: there is a small gap between dropping and creating the trigger. > I prefer to allow database do dirty work by itself. In this case, I have a different opinion, at least currently. I believe your use case is quite special, and I don't think it makes sense to support it within the database at the moment. If more people have similar problems I will change my mind :-) 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 -~----------~----~----~----~------~----~------~--~---
