Hi Marcus,
I'm very sorry for the delay - thank you very much for the ping. Indeed,
this can be reproduced easily. Your original analysis leading to these
lines was correct:
// [#1859] In some databases, not all fields can be fetched via
getGeneratedKeys()
if (REFRESH_GENERATED_KEYS.contains(configuration().family()) && this
instanceof UpdatableRecord)
((UpdatableRecord<?>) this).refresh(key.toArray(EMPTY_FIELD));
That logic should be guarded by a check of
Settings.returnAllOnUpdatableRecord
I have created an issue for this:
https://github.com/jOOQ/jOOQ/issues/7942
I'll fix it today and include the fix in 3.11.6, which should be released
this or next week
Thanks again for your detailed report and for your patience.
Lukas
On Mon, Oct 15, 2018 at 5:39 PM Marcus Gattinger <[email protected]> wrote:
> Hi Lukas,
>
> have you had the chance to figure out, what the problem with the
> additional select was? Do you have any update for me?
>
> Kind regards,
> Marcus
>
> --
> 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.
>
--
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.
