1

Imagine that you are using a wildcard filter '%XXX%' which runs automatically after one second and search across 10K rows datatable with 10+ fields.

From the point of view of infrastructure resources optimization, it seems inefficient to filter a single character because it will send back almost everything in almost any case.

What do you think about the user experience? Does the user expects that the filtering starts with a single character, knowing that most users will probably type 2+ characters anyway? Will it seem strange that the filter does not run when a key is pressed?

Improve this question
2
  • Is a single character a valid and meaningful search in your use case?
    – maxathousand
    Jun 5, 2017 at 21:57
  • I have no idea, it's a cloud service with thousands of use cases, different accounts, various usages. No way to know. Intuitively I would find it strange to filter multiple fields on a single char, but it may eventually happen as Travis pointed.
    – reeax
    Jun 6, 2017 at 10:09

1 Answer 1

Reset to default
0

In many use cases, a single character filter/search is valid. The best way to simplify this is to run the filter when the user starts typing. Wait for a length of time after each key press. If another key is pressed, restart the counter. Perhaps a length between .5 seconds and 1 second would be best.

Improve this answer
1
  • 1
    Thanks for your opinion that a single char may be a valid request. Of course, already have 750ms timeout on key press events :)
    – reeax
    Jun 5, 2017 at 19:14

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.