Steve Ebersole

So you are saying that given that joined for-update query, even delete from books won't be blocked?

Since it is not specified, afaik the default (2PL/LOCKS) should apply - https://hsqldb.org/doc/guide/sessions-chapt.html#snc_tx_tx_cc However, I did not see anything obvious there about the impact, if any, of for-update. Can I assume then that with LOCKS for-update only acquires shared locks? Assuming so, another option would possibly be something mentioned in that above doc - HyperSQL also supports explicit locking of a group of tables for the duration of the current transaction. Use of this command...

joins and for-update

Just saw https://sourceforge.net/p/findbugs/feature-requests/364/ I'll post there

Is the intention to allow configuration to disallow Optional use at all as well?

FWIW, someone pointed out -adjustPriority in the FindBugs code which I tried to add...

Thanks Andrey! As far as Gradle integration anyway, the bigger hurdle is the confidence....

Reference https://hibernate.atlassian.net/browse/HHH-9733 and its linked issues