If the project requires lots of SQL feature that H2's SQL provides, then go with SQL. If you need a very small subset of functions that JaQu can do well in (CRUD), go for JaQu (at your own risk). In the end, I felt that SQL would be the best but JaQu would enable writing your transactions in a more Java-like way but it restricts flexibility.
On Jun 30, 3:52 pm, bart <[email protected]> wrote: > Hi, > > I am seriously considering to use JaQu in a project quite big. > I would like to know the current status of JaQu next to : > - issue 286: Enhancements to JaQu (Patch) > - issue 298: JaQu concurrency patch > - the changes proposed by Shai in this > threadhttp://groups.google.com/group/h2-database/browse_thread/thread/52182... > > Regards, > > bart -- 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.
