Fast full-text searching in Python (job for Whoosh?)

[Dino]

On 3/6/2023 11:05 PM, rbowman wrote:

> It must be nice to have a server or two...

No kidding

About everything else you wrote, it makes a ton of sense, in fact it's a 
dilemma I am facing now. My back-end returns 10 entries (I am limiting 
to max 10 matches server side for reasons you can imagine).
As the user keeps typing, should I restrict the existing result set 
based on the new information or re-issue a API call to the server?
Things get confusing pretty fast for the user. You don't want too many 
cooks in kitchen, I guess.
Played a little bit with both approaches in my little application. 
Re-requesting from the server seems to win hands down in my case.
I am sure that them google engineers reached spectacular levels of UI 
finesse with stuff like this.

> On Mon, 6 Mar 2023 21:55:37 -0500, Dino wrote:
>>
>> https://schier.co/blog/wait-for-user-to-stop-typing-using-javascript
> 
> That could be annoying. My use case is address entry. When the user types
> 
> 102 ma
> 
> the suggestions might be
> 
> main
> manson
> maple
> massachusetts
> masten
> 
> in a simple case. When they enter 's' it's narrowed down. Typically I'm
> only dealing with a city or county so the data to be searched isn't huge.
> The maps.google.com address search covers the world and they're also
> throwing in a geographical constraint so the suggestions are applicable to
> the area you're viewing.