Davide D'Alto
Davide D'Alto
Now that I'm having a better look at this, I'm noticing that PgException actually has several fields with info about the error. Maybe that's enough for us to figure out...
> Just pass through whatever the user specifies, and let Postgres sort it out. I don't see why we need to protect Postgres from receiving parameters it doesn't understand. +1
I don't think Hibernate Reactive needs any specific property supported at the moment. But a user can add anything on the URL and we would like to be able to...
Ah interesting.... but it's not intermittent for us. When we launch the build it happens every time
It also reappeared after that specific commit, I don't know if it can help. Anyway, I guess we can close this issue and we can comment on that one
> Which I assume would be expected Yes, that's exactly what the test is supposed to do.
I suppose we should also check the stateless session, though
Our assertions don't actually check the contexts but the threads. On CI the test run in the same thread and so the exception is not thrown as expected even if...
I think we can close this issue, the problem has been solved.
I've tested again with ORM 5.6.9.Final and it's still not working