You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, as I understand, your wonderful search utility works with a JSON record, downloaded to the client and the entire operation is done withing the browser, correct?
That means no live look up mySQL's queries to bring results as the user types ahead...
is it also possible to get the json formed on the fly, for example, take the 3 letters user has entered and trigger a buildJSON call at the 3rd character, submit to your SQL for a query like bring everything you got that matches those 3 letters in the kind of a JSON your engine wants and then leave the rest of the action be taken care of by your engine.
This way, even if you were to have a 2, 3 hundred thousand record DB, having those 3 characters would significantly reduce the JSON to be dealt with...
Am I sensing your tool correctly?
The text was updated successfully, but these errors were encountered:
Hi @halukkaramete ,
you are right, MiniSearch by itself has no knowledge of PHP or databases. It normally runs in the browser, although it can run on the server side on NodeJS.
It is possible to submit the query to the server for an initial check on the database of the matching records, but that would mean that the candidate records have to be re-indexed upon each query. If the full collection of documents does not fit in the browser, it might be worth using a search server like ElasticSearch.
Hello, as I understand, your wonderful search utility works with a JSON record, downloaded to the client and the entire operation is done withing the browser, correct?
That means no live look up mySQL's queries to bring results as the user types ahead...
is it also possible to get the json formed on the fly, for example, take the 3 letters user has entered and trigger a buildJSON call at the 3rd character, submit to your SQL for a query like bring everything you got that matches those 3 letters in the kind of a JSON your engine wants and then leave the rest of the action be taken care of by your engine.
This way, even if you were to have a 2, 3 hundred thousand record DB, having those 3 characters would significantly reduce the JSON to be dealt with...
Am I sensing your tool correctly?
The text was updated successfully, but these errors were encountered: