Bug #100763 | Workbench not showing triggers on table and cannot edit or delete it 8.0. | ||
---|---|---|---|
Submitted: | 8 Sep 2020 8:35 | Modified: | 15 Sep 2020 10:55 |
Reporter: | Francesco Auriemma | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Workbench: Administration | Severity: | S3 (Non-critical) |
Version: | 8.0.21 | OS: | Windows |
Assigned to: | CPU Architecture: | Any |
[8 Sep 2020 8:35]
Francesco Auriemma
[8 Sep 2020 8:36]
Francesco Auriemma
Example of Dump
Attachment: Dump20200908.sql (application/octet-stream, text), 227.17 KiB.
[8 Sep 2020 8:44]
Francesco Auriemma
Show Trigger in TreeView but not show in AlterSchema Window
Attachment: Show Trigger in TreeView but not show in AlterSchema Window.png (image/png, text), 234.82 KiB.
[8 Sep 2020 8:44]
Francesco Auriemma
Show Trigger on Imported Schema
Attachment: Show Trigger on Imported Schema.png (image/png, text), 436.19 KiB.
[8 Sep 2020 9:12]
MySQL Verification Team
Trigger
Attachment: 100763.png (image/png, text), 181.99 KiB.
[8 Sep 2020 9:13]
MySQL Verification Team
Thank you for the bug report. Please see screenshot prior attached.
[15 Sep 2020 10:55]
Francesco Auriemma
What should I see? Only thing you notice is the incorrect casing that is generated by importing the dump. Please indicate how we can resolve the issue.
[3 Jan 2023 21:49]
Daniel Bond
I have the same issue using Mac Ventura 13.1, Apple M1 Max, MySQL 8.0.31 and Workbench 8.0.23 I have tried about everything I can find but the problem is with Workbench. The triggers can be added via the cmd line interface using the generated code from Workbench. They show up in tree view but not when you alter the table.
[5 Jan 2023 1:08]
Daniel Bond
It looks like it is something to do with the MySQL and not the Workbench. I have the Workbench instance connecting to multiple instances of MySQL on remote servers and on remote servers the Workbench shows the Triggers.