On 27/05/2013 2:35 PM, Noel Grandin wrote:
No, I don't think we need to add extra complexity. We'll figure the locking thing out eventually. Most of the time it isn't a problem because people don't normally try and update the same tables inside a trigger.
Fair enough. The first and third points have a workaround. What about the second point (the user need to know which kind of operation is being fired)? I don't know of a workaround for that... short of creating a separate Trigger class for each kind of operation but this is a really ugly hack. You could always add a new fire() method containing this information that delegates to the old one for backwards compatibility.
Thanks, Gili -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
