Branch: refs/heads/main
Home:
https://github.com/hibernate/hibernate-orm
Commit: 8bd9f9050ea01cc0f825a6c6d3b95e0d30325639
https://github.com/hibernate/hibernate-orm/commit/8bd9f9050ea01cc0f825a6c...
Author: Daniël van Eeden <git(a)myname.nl>
Date: 2026-02-25 (Wed, 25 Feb 2026)
Changed paths:
M
hibernate-community-dialects/src/main/java/org/hibernate/community/dialect/lock/internal/TiDBLockingSupport.java
M
hibernate-core/src/main/java/org/hibernate/dialect/lock/internal/MySQLLockingSupport.java
M
hibernate-core/src/test/java/org/hibernate/orm/test/locking/options/ConnectionLockTimeoutTests.java
Log Message:
-----------
TiDB: Fix usage of innodb_lock_wait_timeout
- In MySQL `innodb_lock_wait_timeout` can be between 1 and 1073741824
- In TiDB v8.5.5 `innodb_lock_wait_timeout` can be between 1 and 3600
- In TiDB maste `innodb_lock_wait_timeout` can be between 1 and 1073741824
This PR adds an argument to `ConnectionLockTimeoutStrategyImpl` to set
the limit of the `innodb_lock_wait_timeout` so it can be re-used by TiDB
v8.5.5
References:
-
https://dev.mysql.com/doc/refman/8.4/en/innodb-parameters.html#sysvar_inn...
-
https://docs.pingcap.com/tidb/stable/system-variables/#innodb_lock_wait_t...
-
https://github.com/pingcap/tidb/pull/65153
Co-authored-by: Christian Beikov <christian.beikov(a)gmail.com>
To unsubscribe from these emails, change your notification settings at
https://github.com/hibernate/hibernate-orm/settings/notifications