You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently you can not get short tree or fast navigate to triggers corresponding to table.
I want see triggers near parent table.
But I do not want see ridiculous long tree as I see now if uncheck "group by type" option for tree.
Describe the solution you'd like
I want check box near "group by type" named as "group by table". If it checked, all children of table go to in table, and collapsed by default. So I can open it if want examine triggers.
If checked both grouping "type" + "table", triggers can be duplicated in tree or goes to subitems to table and sections "triggers" eliminated. Up to you.
Describe alternatives you've considered
This can be or/also implemented as additional subtab for tab "Table: XXX". Maybe Next after subtab "Indexes".
Additional context
Nope.
The text was updated successfully, but these errors were encountered:
Dirty enough fix. But work properly: when use group by types and table has properly named triggers - then plus sign appear and you can view these triggers as subitems of this table.
Not tested fully. Maybe break something.
Is your feature request related to a problem? Please describe.
Currently you can not get short tree or fast navigate to triggers corresponding to table.
I want see triggers near parent table.
But I do not want see ridiculous long tree as I see now if uncheck "group by type" option for tree.
Describe the solution you'd like
I want check box near "group by type" named as "group by table". If it checked, all children of table go to in table, and collapsed by default. So I can open it if want examine triggers.
If checked both grouping "type" + "table", triggers can be duplicated in tree or goes to subitems to table and sections "triggers" eliminated. Up to you.
Describe alternatives you've considered
This can be or/also implemented as additional subtab for tab "Table: XXX". Maybe Next after subtab "Indexes".
Additional context
Nope.
The text was updated successfully, but these errors were encountered: