Bas de Bakker

Why should the conversions to/from character be different? The same timezone is explicitly specified in both setTimestamp and getTimestamp. Shouldn't those conversions to/from character be using those timezones? (Also, it works as expected in PostgreSQL, SQL Server, Oracle, SAP HANA, MariaDB and MySQL.)

Unexpected triggered data change violation

Incorrect foreign key constraint violation exception (again)

PreparedStatement.cancel() just hangs

Foreign key constraint violation when target updated

I can confirm that this issue is fixed in SVN head, thanks.

As you may have noticed I accidentally put the "long k = 0;" inside the for loop. I meant it to be outside, but it fails either way.

Incorrect foreign key constraint violation exception