Bug #105941 using new keyword in after update trigger
Submitted: 20 Dec 2021 16:10 Modified: 20 Jan 2022 16:35
Reporter: floob boogaloo Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:8.0.27 OS:MacOS
Assigned to: CPU Architecture:x86

[20 Dec 2021 16:10] floob boogaloo
When creating an after update trigger and using the new keyword, the system crashes and does not recognize the "new" table.

How to repeat:
Make any after update trigger and try to use the new keyword. However, this may have some interference issues with imported tables or if everything was not made from scratch.

Suggested fix:
Make sure to write everything from scratch, try not to use imported tables. This should not be necessary, imported tables should work with written-from-scratch tables.
[20 Dec 2021 16:35] MySQL Verification Team
Thank you for the bug report. Please provide a complete repeatable test case ( a SQL script ) not just its description. Thanks.
[21 Jan 2022 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".