| Bug #110251 | change information about get_lock error message | ||
|---|---|---|---|
| Submitted: | 1 Mar 2023 12:10 | Modified: | 27 Apr 2023 15:37 |
| Reporter: | bin wang (OCA) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Errors | Severity: | S3 (Non-critical) |
| Version: | Ver 8.0 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Contribution, errors | ||
[1 Mar 2023 12:11]
bin wang
suggested add patch (*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.
Contribution: lock_name_err.patch (application/octet-stream, text), 1.11 KiB.
[1 Mar 2023 12:23]
MySQL Verification Team
Hello bin wang, Thank you for the report and contribution. regards, Umesh
[27 Apr 2023 15:37]
Stefan Hinz
Posted by developer: Fixed in 8.0.34. Error message changed, no changelog entry required.
Description: MySQL enforces a maximum length on lock names of 64 characters. when lock_name length is more than 64 characters in get_lock, error message is below: ERROR 3057 (42000): Incorrect user-level lock name 'xxxxxxxxxxxxxxxxxxx'; Then message is Incorrect lock name, not about length. Change the message about error lock name length is more convenient when trouble shooting How to repeat: mysql> select get_lock('wdnmqkno-dadas--1231-3@efs_01-najvcn-1212-ccasc@mcm-sddd-danjskn111@c0c0-mmm-lll',1); ERROR 3057 (42000): Incorrect user-level lock name 'wdnmqkno-dadas--1231-3@efs_01-najvcn-1212-ccasc@mcm-sddd-danjskn111@c0c0-mmm-lll'. Suggested fix: change error message is more convenient mysql> select get_lock('wdnmqkno-dadas--1231-3@efs_01-najvcn-1212-ccasc@mcm-sddd-danjskn111@c0c0-mmm-lll',1); ERROR 3057 (42000): Exceed user-level lock name limit 'wdnmqkno-dadas--1231-3@efs_01-najvcn-1212-ccasc@mcm-sddd-danjskn111@c0c0-mmm-lll'.