Thanks for the responses, they really help a great deal. *We constantly pass over the manual. Anything you find is greatly appreciated. We hardly need to read our own manual anymore, so feedback from users who do read it for the first time is very useful!*
Manuals should assume no tribal knowledge. People with tribal knowledge don't read them! *Because there isn't any surrounding boilerplate code! :-) **With jOOQ, you don't need any try-with-resources statements. jOOQ manages all JDBC resources for you, internally (except the JDBC Connection, if you want to manage that).* My confusion with the try-with-resources partially was that some jooq objects didn't appear to have implemented closeable. If all I need to do is manage the connection object then that's perfect and makes me want to use jooq even more. Imho they should shoot the guy who invented finally blocks. I was doing backflips in and out of cubicles when they came out with try-with-resources. *Is that what you had in mind? Or in what context would you expect us to provide lambda examples in the manual?* In terms of lambdas, a lot of db work obviously involves processing sets of records which they fit well. I starting to see them employed in framework documentation everywhere, but when I read the jooq manual I just have this sense of reading Java 6 code instead of Java 8 code. Felt... dusty? *And perhaps includes / excludes patterns. jOOQ is a database-first API, so yes, it's true that generated objects are inherently tied to the source database. We see this as a feature, but perhaps we've missed something - e.g. a specific use-case that we cannot cover yet?* *Perhaps I'm missing the 'feature' aspect of it.* *A schema is not inherently tied to any physical database but a record mapping with added validation.* *Conceptually, I think of them as data structures in languages such as C, RPG IV or COBOL that you could use as a template moving it around in memory. **There is no reason I can see where a person should be forcibly restricted from pointing a valid schema abstraction at multiple connections.** I'm sure I'm not the only person in the world doing a data migration. QueryDSL was able to handle this use case out of the box, without any further XML configuration. You simply reference the schema object and the connection when creating the query.* -- 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.
