ository and thus opening up endless bikesheds
> instead of truly innovating, at least in my opinion.
>
> In order to respond to your criticism, jOOQ's approach is the *only* way
> to result in code:
>
> - That is not hard to read
> - That is consistent
> - That is easy to
anguage in a way that
>> would even be idiomatic for SQL itself.
>>
>> An example of 2) is the DAO API, which I regret so much. It is such a
>> terrible bikeshed, being the only really opinionated thing in jOOQ. Sure,
>> users like it, and it can't be removed again for
Hello everyone,
I hope this message finds you well. I’d like to share an idea for a
potential feature request, inspired by a brief discussion on SO with Lukas.
*INTRO* When starting a Java Spring project, developers often use JPA for
data mapping because it allows for quick and
