Re: Whoosh autocomplete search logging for future analysis

You generally would store the necessary information as part of your view, or more likely as part of the form, inside the database for later retrieval. In your scenario though, your AJAX requests should be using GET or HEAD requests, and even the search form itself should be using a GET action, all

Re: Whoosh autocomplete search logging for future analysis

Thanks James. In the case of using GET there seams to be plenty of log analyzers, so we have a lot of options. Any best practice / experience when using POST? I understand we can store the query to the DB, even using django model for that. But I am afraid of the performance hit. Radek On Sat

Re: Whoosh autocomplete search logging for future analysis

Wouldn't all of your AJAX requests be logged in your web server access logs, assuming that you are using GET requests for your searches? You can parse those for analysis. You could also probably configure Whoosh or whatever calls the search function to write a record in the database with the quer

Whoosh autocomplete search logging for future analysis

Hi, what is the best practice to setup the logging of search autocomplete logging for future analysis? When using Whoosh as a search engine and django. The search is searching within hundred thousands of product names. We want to get the insight on typos and typical name abbreviations. The a