Congrats to your tool. Using method references is quite clever, reminds me of a couple of tools that did something with instrumentation and advanced reflection

Congrats to your tool. Using method references is quite clever, reminds me of a couple of tools that did something with instrumentation and advanced reflection (cglib, I guess). These come to my mind: OhmDB (http://www.ohmdb.com http://www.ohmdb.com) LambdaJ (https://code.google.com/p/lambdaj/ https://code.google.com/p/lambdaj/) JaQu (http://www.h2database.com/html/jaqu.html http://www.h2database.com/html/jaqu.html) JIRM, I think, also played around with similar ideas (https://github.com/agentgt/jirm https://github.com/agentgt/jirm) Comparing this approach with jOOQ (http://www.jooq.org http://www.jooq.org), I think that method references might be somewhat limited in a SQL sense of thinking. How would you handle aliases? E.g. how would you perform a self-join, such as: FROM person p1 JOIN person p2 ON p1.parent_id = p2.id