In my current project I work with ~150 tables. Navigating between them is a pain.
Usually I use only ~5 tables but sometimes this 5, sometimes that 6. So, the star icon is not good for me to filter them.
It would be amazing, however, if I had a list of recently used tables. I am thinking of a solution which is similar to the Libre Office solution around the recently used fonts. Normally the list of fonts contains the font names in alphabetical order but as I start to change fonts in my document, the used font names are repeated on the top of the list.
In HeidiSql, I would like to see a separate panel which occupies the upper part of the left panel which contains the table names now. See the attachment for better explanation. Do you think it is solvable?
Recently used tables
HeidiSQL provides
* stars for favorite tables
* a table filter with regex capabilities
* groups with object types
* highlighted icons for tables which were clicked at least one time in the current session
One of these features should do what you need. I highly recommend to use the table filter. It's really useful with its regular expression support.
* stars for favorite tables
* a table filter with regex capabilities
* groups with object types
* highlighted icons for tables which were clicked at least one time in the current session
One of these features should do what you need. I highly recommend to use the table filter. It's really useful with its regular expression support.
Hi Ansgar, thank you for your response. I knew all of these possibilities, apart from the regexp usage in the table filter. It is good to learn new things. ) However,
- The stars are useful if you know _in_advance_ that you will use that table soon. I rarely can predict this. I recognise many times that I should jump back to the table I just used two minutes ago but I didn't star it because I didn't expect using it again. Anyway, after a while all the tables get stared which makes it useless. :)
- The regexp is good if the table names are similar. I really love the table filter and I do use it too. But the problem I described above cannot be solved by this.
- The groups are not good for my purpose. In my present project I have 150 tables, 50 functions, etc. In one group (the tables) there are too many objects.
- The highlighted icons are the closest to what I wish but if you have 150 or even more tables then you have to scroll them to find the highlighted icons. Half a year ago I was working in a project where there were almost 400 tables. It means that the table names are listed through 8-10 screens.
If you have so many items in the actual group then none of the highlighting/indication saves you from scrolling. This feature would really help me a lot. Can is ask this, please-please-please? :)
- The stars are useful if you know _in_advance_ that you will use that table soon. I rarely can predict this. I recognise many times that I should jump back to the table I just used two minutes ago but I didn't star it because I didn't expect using it again. Anyway, after a while all the tables get stared which makes it useless. :)
- The regexp is good if the table names are similar. I really love the table filter and I do use it too. But the problem I described above cannot be solved by this.
- The groups are not good for my purpose. In my present project I have 150 tables, 50 functions, etc. In one group (the tables) there are too many objects.
- The highlighted icons are the closest to what I wish but if you have 150 or even more tables then you have to scroll them to find the highlighted icons. Half a year ago I was working in a project where there were almost 400 tables. It means that the table names are listed through 8-10 screens.
If you have so many items in the actual group then none of the highlighting/indication saves you from scrolling. This feature would really help me a lot. Can is ask this, please-please-please? :)
Sorry, I don't think that's something HeidiSQL is really missing.
You should really play with the table filter. I find myself often doing the same in a large Magento database with ~500 tables. What about these:
^(sales_flat_or|expo|cli|soap)
^(rating_(option_vo|store)|review_(entity_s|store))
The filter input even has a history dropdown, where you can recall previous filters.
You should really play with the table filter. I find myself often doing the same in a large Magento database with ~500 tables. What about these:
^(sales_flat_or|expo|cli|soap)
^(rating_(option_vo|store)|review_(entity_s|store))
The filter input even has a history dropdown, where you can recall previous filters.
Please login to leave a reply, or register at first.