Hello guys! We are a new startup and decided to try jOOQ instead of JPA in the backend of our first product and we haven’t regretted it so far. We wrote a blog post summarizing our experiences and thoughts with jOOQ here <http://teonos.com/blog/java/development/2014/11/10/experiences-with-jOOQ.html> .
The biggest minus with using jOOQ so far has been the “join deduplication boilerplate” issue I mention in the blog post. Does my suggestion of adding some basic association support between the generated Record types make sense to anyone else? E.g. using my blog example: that a CustomerRecord can hold a list of OrderRecords? The next step would then be that I could automagically convert a Result of a CUSTOMER.leftJoin(ORDER) query into CustomerRecords with the orders populated. Currently I have to write this logic myself, repeatedly in slight variations and it feels like it's boilerplate that could perhaps come with the library. Looks like at least some of the Python ActiveRecord implementations support associations to some extent (SQLObject <http://sqlobject.org/SQLObject.html#one-to-many-relationships>, SQLAlchemy <http://docs.sqlalchemy.org/en/rel_0_9/orm/loading.html>). I'm not looking for automatic fetching of associations (and the can of worms that comes with), just something that would simplify the step of converting JOIN results into Records with associations. Regards, Oskar Norrback -- 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.
