Do not show triggers in database view
I think it's better to show it as sub-nodes of the table, like in MySQL-Front.
What about adding a new tab in the table designer, beside the "Foreign keys" one? It could list the table's triggers and link to the current trigger designer.
And when seeing the objects in the database, I can find them more quickly when they are sorted by type: first tables, then procedures, then functions, and so on...
Thanks for your answer, and sorry for my english!
I would like to rise up this issue again.
I want to join the idea of trigger visually linked its table. Just for better user experience.
Today, since HeidiSQL supports various databases, it really doesn't matter how MySQL handle triggers.
I'd like to ask to add new tab for triggers to table editor window.
Another suggested way is to add children items to table tree. It could contain equivalent of the tabs. MySQL QueryBrowse as well as pgAdmin does it this way.
Please note that this request is really justified. Just imagine thousands of triggers vs hundreds of tables with a few triggers each.
Point is, that all triggers (in particular schema) are collected in branch
schema > triggers
while it would be better to split them and show under:
schema > tables > particular_table > triggers
I hope we both agree such arrangement is logical since (row) triggers can't exist without a table and might considered as table "children"
Please login to leave a reply, or register at first.