Meteor-Community-Packages / Meteor-Community-Packages/meteor-tabular
Problem with multi-column search
- Dominant language
- JavaScript
- Stars
- 360
- Forks
- 132
- PR merge metrics
- No merged PRs in 30d
Description
First of all, let me start by saying this component is AMAZING! This saved me lots of programming hours.
I'm now trying to implement individual column searching, as specified by the DataTables documentation on https://datatables.net/examples/api/multi_filter.html, but I'm unable to make it work properly. It seems the search function will work correctly if the data is all in memory, but it seems to fail when the data is loaded from the server.
I'm not really sure this is an issue on the DataTables component itself or something you can fix here, so please feel free to direct me to the proper help channel if needed.
Right now my code is implemented exactly as found in the documentation I pointed above, but the search works only on the first column I try whatever it is. From the second column on, the search is returning something I cannot identify. With my data, the first search (which is a username) returns a total of 987 documents. The second criteria alone (which is a table name) returns a total of 292,056 documents and both should return 27 documents ($and) or 293,016 documents ($or) but the table info gives me back 286,126 entries which I cannot understand because it doesn't fits any logical criteria.
Can you help? What I could possibly be doing wrong?
Thanks in advance,
/Edson
Contributor guide
Research direction
The issue names no repository files or tests. Start with the DataTables multi_filter example linked in the report and reproduce the behavior using server-loaded data, checking the first and subsequent column criteria and returned counts. Done requires identifying whether the component or the usage causes the unexpected combined-search results, with a reproducible conclusion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100