JaQu in SVN has the option to define a custom dialect for a particular database. Currently there is only one implementation of SQLDialect and that is for H2. For supporting other DBs you should start there.
You should also be aware that JaQu has some H2 class dependencies so at present it requires the H2 jar as well (1.3MB). Its not hard to remove these dependencies. It also shouldn't be hard to adjust the build definition to make a stand-alone JaQu although last time I tried that approach, JaQu ended up needing way more of H2 than it really should have because of class verification errors of the pulled-in dependencies. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/mosvL8qDxB8J. To post to this group, send email to h2-database@googlegroups.com. To unsubscribe from this group, send email to h2-database+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
