On Thursday, November 27, 2014 7:31:14 AM UTC-5, Lukas Eder wrote: > > On a more serious note (sorry, couldn't resist 5 minutes ago) > > I'm sorry to see you go because of this. I do believe that you will find > the missing features limiting after a while, but I certainly understand > that moving a project forward can be essential. > I'm curious about the "bit slower" part. How does this manifest? > >> >> > This project was just a database migration, so QueryDsl worked. Less features true, but the overall interface was simpler as a result. QueryDSL doesn't really have a manual like Jooq does, but I didn't need one.
I hope you find time to make a pass over the manual by the time I come back. I *really *want to use Jooq for crud, but most of the examples look like Java 5-6 era and are in serious need of being brought up to date. Other than my binding issue, I couldn't find an example that used try with resources in the manual, as everything is missing surrounding boilerplate code. I also couldn't find an example that leveraged lambda expressions. Nor could I find out the best practices in using the same schema for two different databases. It worked out of the box with querydsl, but jooq didn't appear to like it at all. Unlike QueryDSL, the jooq generated java objects appeared inherently tied to the source database My workaround was to generate two separate schemas, renaming the mysql enum fields on the target db. Not pretty, but it did work! In terms of the 'bit slower part: I haven't captured metrics, but it's just my perceived experience based upon dumping oodles of records through each over many iterations. The difference is that I'm not using foreign keys to lookup child records in querydsl, but an actual secondary query. I imagine that might be one of the missing features, as it wasn't at all clear how to do it from the interface. -- 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/d/optout.
