Georgii

@gagabu I have looked, and for the Postgre Debian docker image, its Debian version doesn't have Europe/Kyiv as an available timezone, so that is the probable reason why this doesn't...

@chinskiy I think Java 11 didn't have Europe/Kyiv, so the old value was passed. After the upgrade to Java 17, it started using a new one, making the connection fail.

We are reverting to Java 11 in 23.0.0, so the issue should not be actual for some time. Maybe it will arise again if Java 17 is used again.

@vvrnv Unfortunately, We can't do anything to resolve this situation. If the issue happens again, please feel free to reopen the ticket.

> Kerberos > Deprecate 3DES and RC4 in Kerberos > > 3DES and RC4 Kerberos encryption types have now been disabled by default. Both 3DES and RC4 are weak encryption...

Attached the screenshot

@podoni, Hi, it looks like it can happen due to a comment in the query. Can you try to launch the query with it removed?

Well, it looks like there are three possible cases when read-only is applied. I confirm the case when we have `select` with repeated columns and for queries with comments. @jonylim...

Confirmed for Community Edition.

Unfortunately, this is related to the community edition's inability to handle gis values from the SQL server. This functionality exists in DBeaver PRO, which specifically allows handling Oracle and SQL...