> small gap between dropping and creating the trigger I clearly understand this problem, but for my particular case triggers should not be changed at runtime in production, only for simpler testing and debugging purposes. My second suggestion with "alter trigger" would solve this.
> I believe your use case is quite special... If more people have similar > problems I will change my mind :-) Yes, my use case may be special while I don't use H2 as usual relational data storage but as data buffer with processing capabilities, but I think all the people will agree with me that parametrized logic is much more convenient and flexible than hard- coding and good if it is supported out of the box without any additional crooked nails. Also I don't think that this feature can break something or make really slower or harder.. I'm also invite others to say a word on this. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
