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
Super helpful project!
Would be great to see a minimum input length parameter before the search would get set to the database. I use this for addresses and for example when searching for 123 main st, I dont really want to be searching for 123 as I am tying so maybe setting the limit to 4 or 5 characters it would reduce the first lag I see on the results (even with a gin index).
The text was updated successfully, but these errors were encountered:
I would counter this by adding that the conception of the plugin is to seach a single address string and pull out any data that meets part of the typed criteria. Limiting that would removed the intension of the plugin - what you need is a multi-column search facility and that isn't what this plugin is. I would strongly argue against this request.
@rugbygis I am not sure I follow that logic. I do not need multicolumn search, our addresses work fine searching as is. I am just under the impression that adding a limit capability would just not kick off the search until a certain amount of characters is input. I would assume setting this to a default of 0 would not change your result from what they are currently.
Sorry. I thought you meant having the restriction as a default. You are absolutely right, having the ability to not search until a number of characters had been reached would be an advantage based on the data you were searching so I apologise for the post and didn't mean to diminish your suggestion
Super helpful project!
Would be great to see a minimum input length parameter before the search would get set to the database. I use this for addresses and for example when searching for 123 main st, I dont really want to be searching for 123 as I am tying so maybe setting the limit to 4 or 5 characters it would reduce the first lag I see on the results (even with a gin index).
The text was updated successfully, but these errors were encountered: