[BUG] Unique values + count not on the filtered dataset but on entire table

[expired user #8144]'s profile image [expired user #8144] posted 9 years ago in Feature discussion Permalink
Hey Ansgar,

Sorry for crossposting but I was not so sure you were still using the google bug tracker. There is no link or reference to it from your website - I had it bookmarked from before.

So here it is: http://code.google.com/p/heidisql/issues/detail?id=3668 and appreciate your feedback.

Let me/us know how best to report bugs going forward.

Thanks,
Yannick
ansgar's profile image ansgar posted 9 years ago Permalink
The tracker has more tickets I ever can handle. I have tried to reduce them by fixing things but as soon as I fix one there are three new ones. Also it is a time stealer to handle the myriad of duplicate reports.

So, you say the quick filters in the "More filters" submenu should reuse an existing filter. Sounds like a good idea.
[expired user #8144]'s profile image [expired user #8144] posted 9 years ago Permalink
Yes, intuitively one would expect the quick filters to apply on the displayed dataset which may be filtered already. Also would it be possible to extend the quick filter functionality to queries ? It is disable today.
ansgar's profile image ansgar posted 9 years ago Permalink
No, queries are user-defined, and as soon as the query is not an ordinary "SELECT xy FROM table", HeidiSQL would not know where to get results from.
Code modification/commit from ansgar.becker, 9 years ago, revision 4881
Use existing data grid WHERE filter to filter values from quick filter > "More values". See http://www.heidisql.com/forum.php?t=17086
ansgar's profile image ansgar posted 9 years ago Permalink
Done in r4881
[expired user #8144]'s profile image [expired user #8144] posted 9 years ago Permalink
Thanks Ansgar for r881.
For queries, I am not sure I understand the challenge:
1. Consider query: select a.text1, b.text2, b.text1 from a join b on x=y
2. if user could select a quick filter on a given column, can HS not read the column header e.g. a.text1 and add a WHERE clause for that field, or amend the clause if it is already in the query statement ?

There is only one case I can think of where the WHERE criteria is not that straightforward namely if field is a calculated field as HS would need to use the formula to filter on.

Can you give an example of a query so I can better understand the issue at hand.

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