Sehrope Sarkuni
Sehrope Sarkuni
> On the other hand, threading issues (e.g. reusing a connection across threads) are quite common, so adding some safety still makes sense. Not if it's going to be for...
I can break the tie by suggesting we drop both and go back to just Java ;-)
I really walked into that one ... You mean just this directory? https://github.com/pgjdbc/pgjdbc/tree/master/test-gss/src/main/groovy
That doesn't look too bad. It's just a couple files and self-contained. Sure I can get to that.
> Exactly. I think semver should be used to signal the amount of changes to the end-users, and semver should not be used as an excuse for breaking things. +1....
> We have to specify what is going into a release and not allow creep . +1 to regularly scheduled releases. It's helpful both from the perspective of contributors and...
Check that you are supplying a password. The error is happening because `password` is null but it needs a non-empty value to perform the SCRAM authentication. We can improve the...
I don't think you can have a "null" password with SCRAM. Pretty sure an empty string wouldn't work either. It needs to be a non-empty value. If you do not...
Is that the actual function? If so, then you'd need to change it to await the individual `client.query(...)` calls to ensure they get completed prior to the next one. If...
No, the `client.release(...)` function is sync so the await in my example is not needed. It shouldn't change anything either way though. See if the actual task being done with...