think it is pure luck that it works with most jdbc drivers!

I can confirm that with Oracle, SQL Server, MySQL, MariaDB, PostgreSQL and H2, the bug does not replicate. It's JDBC standard, after all.

Try running the test that I wrote on SAP HANA and confirm that it fails. Also, please provide some screen capture or stack trace so that I can investigate further why SAP HANA behaves differently than how JDBC Drivers are supposed to work.