Thanks for your nice contribution Roger! 2013/6/30 Roger Thomas <[email protected]>
> When looking for a solution I first found Empire-DB, but what caused me to > look for an alternative (hence why I'm around here) are > > 1) I found the documentation was more aimed at people who already > understood it, while jOOQ's provided a far better entry in its environment. > > 2) Empire-DB does not have a code generator (and I hate doing boiler > plate coding). jOOQ's generater is a great solution for ad-hoc development > cycles as well as larger formal projects. > The fact that once you have the XML configured for the generater > you can write code as shown here > > > http://www.jooq.org/doc/3.0/manual/getting-started/tutorials/jooq-in-7-steps/jooq-in-7-steps-step6/ > > No maintaining XML files or java classes to map the schema before it > can be used. > > 3) jOOQ is better at managing cross target database coding as it tries > to fill in the gaps between different SQL implementations. > > 4) Empire-DB does not try to emulate all of the SQL syntax so you have > to understand a different syntax for say UPDATE, while jOOQ tries > its best to map SQL syntax into the Java environment. (I have a > very strong SQL history so like to scan SQL 'like' syntax). > > > While saying all of the above I do think that the main thing that > currently gives jOOQ the advantage is the drive shown by Lukas. Fixes, > updates and general communications > always makes or breaks an open source project and Lukas's commitment is > A+. The differance in part I think is due to the fact that Lukas has a lot > of future plans, while the team > looking after Empire-DB are more focussed on maintaining a current product > than adding any major changes. Yes, my commitment is strong. In fact, I'm currently evaluating the "next steps" of professional OSS development, thinking about how to provide services such as: - basic professional support - premium professional support (later on) - custom engineering - on-site trainings - "shared" trainings, such as the upcoming one in Zurich in September (in German): http://www.ch-open.ch/wstage/workshop-tage/2013/aktuelles-programm-2013/ws-6-mit-jooq-und-opensource-datenbanken-sofort-produktiv-werden/ And much more. If you like it or not, you're going to hear 1-2 things about jOOQ in the near future :-) My goal is that within 3-4 years, Java / SQL developers will be asking themselves: Should I use JPA or jOOQ for the problem at hand? - JPA will be the right choice for "top down", application-domain-driven engineering. - jOOQ will be the right choice for "bottom up", database-model-driven engineering. I will announce all of this more officially, once I have settled for a service infrastructure and strategy. Cheers Lukas -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
