Hi Tim, sorry, I cannot really say anything about Spring Boot as I am not using it. But I can say that I have used JPA and when you really need control over your statements and take advantage of the power of SQL and your database it's really not what you want to use. It's sufficient for simple things, but when things get more complex it's just a complete failure.
JOOQ is more like Empire-db but IMO it still lacks some flexibility concerning dynamic query generation due to the limitations implied in its DSL (domain-specific language) approach. You can easily write your SQL-statement in one chunk of code, but if you need to add extra select fields, constraints and joins depending on certain conditions it gets fiddly. Regards, Rainer > from: Tim Colson [mailto:[email protected]] > to: [email protected] > re: Spring Boot & EmpireDB & JOOQ > > I've been using Spring Boot for a couple of months, and I like it enough that > I'm migrating over an Apache Click app which also uses EmpireDB. > > Spring Boot has tight integration with JPA, and it seems to work fairly well, > but I'm interested in hearing from anyone with experience hooking > EmpireDB into Spring Boot. > > Related to this, just saw an article on JOOQ for read-only queries. Looks > similar in style to EmireDB, yes?
