On 19 Jan 2012 20:26, "Gary Gregory" <[email protected]> wrote: > > So why not use Hibernate or any JPA provider? > > Gary
Plenty of reasons, such as the library's simplicity and the control it affords. And I don't want the lazy-loading, 1st-level cache, etc. it provides. However, there are 2 big missing pieces: reducing the amount of duplication in SQL (which makes refactoring the code or the DB difficult) and mapping joins. Arguably, SQL generation is out of scope. Joins, however, shouldn't be. I think JPA annotations Out of curiosity, how do you guys manage the SQL strings and the joins in your projects? Moandji
