On Thu, Nov 12, 2020 at 6:35 PM Maurizio <[email protected]> wrote:
> I'll try this fix and see if I can switch to 3.14. > > I'm happy to report that the problem in the title and at the origin of > this discussion has been fixed with > https://github.com/jOOQ/jOOQ/issues/10928. > Thanks again for the confirmation. > As a side note, I suspect there is an occasional tendency of jOOQ to > swallow exceptions and, in so doing, obfuscating the problems. This is one > case: I got no exception in my application, only in the MCVE. Running my > application, what I saw was that a field was "null" when it should have not > been. It was fetched, an exception was thrown during the mapping, but I had > no trace of it. > Yes, that design flaw might be addressed in a future major release 4.0. org.jooq.tools.Convert tends to turn values that cannot be converted to the target type into nulls, rather than throwing exceptions. There are a few open issues discussing this. Nothing we can do in the short term without breaking many applications out there. > Another problem that I currently have, is that, if I run several > concurrent read-only transactions, many of them will fail. But if I run the > same multi-step queries without placing them inside a transaction (it's not > really needed, at this moment, it's just future-proofing), they work just > fine. When debugging the transaction, I see there is an exception > somewhere, but I still have to manage put my hands on the original one: I > just see successive, generic, exceptions thrown by jOOQ. More on this topic > in future. > Well, you know the drill :) Not much I can say about that from this description, except, I don't think that sounds like something we're aware of. Best Regards, Lukas -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/CAB4ELO5bAdi%2BTvsOyB9M%2BWGm03nbToCLjHPcwuBdRY7i%3DvF2UA%40mail.gmail.com.
