Shared filter history
Brought to you by:
ansgarbecker
Originally created by: mattias....@gmail.com
As of version 4, the filter history (reintroduced in
https://code.google.com/p/heidisql/issues/detail?id=637) seems to be table
local.
When using foreign keys I find myself using the same filter for multiple
tables very often, so please make the history global again. (I actually use
it so often I may need to stick with 3.2 otherwise)
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: a...@anse.de
Although that's not definite I'm nearly sure the data tab and its filter history will
ceise to exist sooner or later. We're planning to make the query tab results editable
which then works as a replacement for the data tab.
See also
* issue #443
* issue #436
* issue #723
Apart from that the "local" filters were implemented with regard to usability - I
would bet 100 other users will barf if we revert the filters to be global...
Status: WontFix
Related
Tickets:
#436Tickets:
#443Tickets:
#723View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: mattias....@gmail.com
Could local/global be made an option???
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: rosenfie...@gmail.com
If the filter history was changed to include all filters, then for most users, that
would simply mean a lot of filters shown for each table that just doesn't work.
We could change the filter history to show a separator, and then filters meant for
other tables that happen to actually _work_ on the current table.
But that would require an algorithm to check whether a filter can apply to the
current table. Which is basically a matter of checking whether the columns the
filter refers to exists in the chosen table.
The easiest way to implement that algorithm would probably (?) be to alter the
filter GUI so that you're not entering raw SQL, but instead have a list of
criteria. A '+' button adds a new restriction, which is per default AND'd with
other restrictions in the same filter. The list of restrictions then contains a
list of columns, that can be checked against a table to see if a filter fits.
It looks doable, but I don't think anyone on the dev team has time for the task
right now.
Status: Accepted
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: a...@anse.de
(No comment was entered for this change.)
Status: WontFix