New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add fetchOne(RecordMapper) shortcut method to ResultQuery #3810
Conversation
…nt it in implementing classes
Thanks for the suggestion. As we're dual-licensing jOOQ, we need to ensure that rights to non-trivial contributions are properly transferred before I can look into merging your pull request: If you're OK with such an agreement, please e-sign the above document. If not, that's perfectly fine. We can simply implement suggestions as well... |
If I sign the agreement, do you guarantee that my personal informations On Wed, Nov 26, 2014 at 10:56 AM, Lukas Eder notifications@github.com
Laurent Pireyn |
Yes, we guarantee that we will not use or transmit your personal information. We only need this information to identify you or the legal entity you represent in the context of this agreement. |
Thanks. I signed the agreement. On Wed, Nov 26, 2014 at 11:48 AM, Lukas Eder notifications@github.com
Laurent Pireyn |
Thank you very much, and thanks again for the useful contribution |
[#3810] Add fetchOne(RecordMapper) shortcut method to ResultQuery
You're welcome. Thanks for jOOQ which is an amazing lib! Are you interested in pull requests that would be optimizations across all On Wed, Nov 26, 2014 at 12:06 PM, Lukas Eder notifications@github.com
Laurent Pireyn |
Of course!
Well, that would be a bit of work. Is the gain really significant? |
I work with IntelliJ, and it can automatically fix these issues in one These are obviously tiny optimizations, and the gain is probably On Wed, Nov 26, 2014 at 12:42 PM, Lukas Eder notifications@github.com
Laurent Pireyn |
The problem with pull requests to the jOOQ Open Source edition is that we have to merge them back to the "master" repository - the commercial jOOQ edition. I have an IntelliJ license as well, so if you can give me a pointer, I'd prefer to do this particular change myself... I think it's a thing worth pursuing as jOOQ is used at a very low level of client applications and thus might have a lot of impact - even if its just a sub-percent optimisation. |
Btw: Let's continue discussing this issue over here: #3816 :-) |
No description provided.