First, I should say that I really like H2. The SQL syntax is flexible and sensible, the performance is good, and the featureset is extremely rich. It looks especially good in comparison to Derby, which it surpasses in basically every way.
With one exception: SQL-based triggers and stored procedures. I've tinkered a bit with H2's java-based procedures, but I just can't figure out how to use them for what I want, and the limited documentation isn't helping much. Is there any way to hack in SQL procedures using the existing features OR store SQL snippets within the database and then execute them? If not, could I get some additional pointers on how to use the Java- based UDFs/Stored Procs to do more advanced stuff? I'd like to be able to do the usual things, such as conditionally picking which tables to select a value from, doing input validation and conditional errors in response to invalid inputs, and modifying one table in response to changes in another. You know, the usual stuff. But, I'm not crazy about creating a separate java class for every tiny trigger or stored procedure. Thanks, Bob McGee --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
