I use it in a project quite extensively as a replacement for jdbc. It is a lot quicker and nicer to code than jdbc!. It does take a little bit to learn how it works, but once you get it, it is quite intuitive.
Things to look out for. It doesn't do updates, only inserts, selects and deletes. Sometimes handles true and false a bit strangely depending on how you write the statement. Selects with joins take a little bit to get used to, but just follow the examples and it is ok. Biggest thing is that it doesn't do updates so you need to code them with JDBC. It doesn't have any inbuilt transaction stuff, so it is just on autocommit. It works, and it is good to use, but expect that there might be bits missing that you want to use (you can add them yourself), and you can't rely 100% that it is doing the right thing because it hasn't been extensively tested. I have only tried it with H2, not with any other dbs. I've added a few things to it myself to get extra functionality when needed. It is a bit hacky, so I haven't shared it, but it is easy to extend. Ryan ArturoMS wrote: > What issues I would be able to have, if i use jaqu in a simple prject? > what is the missing thing in jaqu? > > For mi looks great,but ... > Which is the hidden danger? > > What do you suggest me? > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
