distal-attribute
distal-attribute
distal-attribute
distal-attribute

Separate the table names from the views, triggers, functions, etc.

User, date Message
Written by tamas9
4 years ago
Category: General
3 posts since Wed, 08 Sep 10
Hello

I would like to ask you to sepatare the table names from the views, triggers, functions, procedures, etc. because in great databases difficoult to find the triggers/functions in the list.

Thanks
Written by ansgar
4 years ago
4936 posts since Fri, 07 Apr 06
Two things:
a) you can currently sort by type, when having the "Type" column visible (right click column headers if it's not there). This might help out a bit.
b) separating them into "folders" is issue #1031
Written by tamas9
4 years ago
3 posts since Wed, 08 Sep 10
Ok, but I would like something like this http://www.heidisql.com/screenshots.php?which=stored_routines.
In the tree view the tables, procedures, functios and triggers are separated.
Written by ansgar
4 years ago
4936 posts since Fri, 07 Apr 06
Please read issue #1031, as said, this is what you mean if I didn't misunderstand you.
Written by x2A
4 years ago
14 posts since Fri, 22 May 09
Hi,
Firstly, great work (as ever), have come back to doing sql-side work after a few months away so thought I'd see how Heidi's progressing, am liking the multiple connections in the tree, and not sure how long you've had the keyboard shortcut config, but is the first time I've noticed it which'll make a lot of working with it smoother. Only one thing I'd say is that a 'back'/'forward' key would be great, so if needing to jump back to the last table being looked at in a database of a hundred tables, the 'back' key would reselect the last item in the left tree that was selected.

But I digress. I apologise if this is answered on that issue #1031 link you posted, Google Code is actually down at the moment (shock!) but if it is on there, just ignore me here, I'll check your Google Code page again in a few hours to see if Google's recovered. When trying to figure out what's going on in a large database, it would be helpful to see which triggers are fired by a table somehow. Either (ideally) by making them subitems in the left hand tree, or (I'd imagine more easy to implement) as a tab in the Table: tab on the right, or of course you may have other ideas.

Anyway I know you can't pander to individual requests, so I just thought I'd register my interest, so if circumstances and desires allow, it may appear one day.

Thanks again,
Alex
 

Please login to leave a reply, or register at first.