Bug #76097 | MySQL Workbench is case sensitive to find existing triggers linked to tables | ||
---|---|---|---|
Submitted: | 2 Mar 2015 14:08 | Modified: | 3 Mar 2015 10:49 |
Reporter: | Equipe Système | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 6.2, 6.2.4 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | triggers |
[2 Mar 2015 14:08]
Equipe Système
[2 Mar 2015 14:50]
Peter Laursen
Trigger names in MySQL are case sensitive if file system on the server is case sensitive. Are you connected to a server running on Linux (for instance) or is it a local server on Windows? -- Peter -- not a MySQL/Oracle person
[3 Mar 2015 10:49]
MySQL Verification Team
Hello Equipe Système, Thank you for the report. Observed this issue when MYSQL server was hosted on windows host. Thanks, Umesh
[3 Mar 2015 10:52]
MySQL Verification Team
// How to repeat ( Repeated only on Win7 with WB 6.2.4 ) use test; create table TEST(id int not null); CREATE TRIGGER test_AFTER_INSERT AFTER INSERT ON TEST FOR EACH ROW BEGIN END; // Try to confirm if trigger exists Right click on table->Alter Table-> Triggers (TAB) ^^ trigger is not listed Where as if you navigate from schemas->test->tables->test->triggers <-- trigger is listed (also, you can confirm the same with information_schema.TRIGGERS)