Jaymer wrote
So, this works as desired in the first post?
What is the performance on a real dB table?
Does it go back to the dB to find these unique values, or only show unique’s from what’s on the page (ie. If Aware is paging and has 50 recs on Page 1, do the unique values come from only Page 1)?
So I really just set it up as a quick test to see if it functions and it does-ish.
My biggest gripe with it is that the sorting is wonky. The results sort however the grid is sorted.
Performance wise I just tested it on a test table of mine with duplicated data from a real one and it was crap. It took 16 seconds to run through the table which is an inventory catalog with 27000 rows and 310 distinct values in the column I tested.
It does go and find all the unique values in the table for that column even if you paging 50 of the 27000 recs at a time.
This is a message from the Kendo UI document that I assume is relevant to the performance issue:
If you have enabled the columns.multi option and your Grid uses serverPaging (or ServerOperations(true) when using the MVC wrappers) you will need to provide columns.filterable.dataSource. Otherwise, a negative impact on the performance could be observed.
I was going to explore its suggestion a bit further.