Bug #110417 | Stored Procedures call locking | ||
---|---|---|---|
Submitted: | 17 Mar 2023 18:47 | Modified: | 20 Mar 2023 12:55 |
Reporter: | Luca Scomparin | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Stored Routines | Severity: | S2 (Serious) |
Version: | 8.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[17 Mar 2023 18:47]
Luca Scomparin
[20 Mar 2023 12:55]
MySQL Verification Team
Hi Mr. Scomparin, Thank you for your bug report. However, you have not set the attributes of all of your stored routines so that changing table can be expected. Please, read our Reference Manual.
[20 Mar 2023 13:56]
MySQL Verification Team
Our Reference Manual describes many restrictions imposed to stored routines, by SQL standards and hence by MySQL. Among others: Statements that perform explicit or implicit commit or rollback, like INSERT. A stored function or trigger cannot modify a table that is already being used (for reading or writing) by the statement that invoked the function or trigger. Not a bug.