Hi, I like the idea, however I would prefer not to add new syntax. Other databases such as MS SQL Server or Oracle support similar functionality without adding new syntax.
Let's discuss about what features are useful / needed first. > Basically a timer thread that can start jobs to start/stop/backup/run_scripts > or call UDFs over a target H2 database. I understand creating a backup of a database (file backup and / or the script) automatically is useful. Running 'analyze' is also useful, but H2 version 1.3 already does that automatically now. One feature that's currently not possible is defragment a database (currently it's only supported using 'shutdown defrag' but not yet while the database is open). What else would be useful? I would like to have concrete use cases (not abstract ones such as "call a method"). > CREATE TASK [ SQL | SCRIPT | MODULE ] taskId AS [sqlText | scriptFilename | > moduleName ] WHEN timeTriggerExpresion ; > 3) As a new trigger type (TRIGGER ON TIMER) implementation. This is new syntax I would like to avoid (unless there is a standard for it). > 1) Completely decoupled server that handle H2 at jdbc connection level. I think it could be within a database. That could be an in-memory database in theory, but you probably need to persist the configuration (when to run what), so a regular database makes sense. > 2) As an extension of actual DatabaseListener with a new TimerEvent every n > millis. As for "auto-backup", the "every n millis" is not user friendly. I guess it would be more user friendly to support crontab syntax. I have some code somewhere to parse that, including a simple scheduler. I will check. 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.
