Hey Marcus, thanks for the quick response on this.
I had ran into the number data type while reading through the documentation as well. Unfortunately, we do specifically want the ability to query using the fuzziness , and the ‘auto-complete’ / type-ahead feature that autocomplete provides. And I don’t -believe- (I could be wrong here), that querying numbers allows for those same features.
Regarding the idea regarding creating an additional field in mongo for storing the 'string'-ified version of the number, this has come up as an option internally as well, and it may be what we do in the short term, but obviously this is not ideal, since we will now need to maintain an additional field whenever we are doing updates/inserts, etc.
Appreciate your responses, and look forward to working with you some more in the future!
Hey Marcus, thanks for the quick response on this.
I had ran into the number data type while reading through the documentation as well. Unfortunately, we do specifically want the ability to query using the fuzziness , and the ‘auto-complete’ / type-ahead feature that autocomplete provides. And I don’t -believe- (I could be wrong here), that querying numbers allows for those same features.
Regarding the idea regarding creating an additional field in mongo for storing the 'string'-ified version of the number, this has come up as an option internally as well, and it may be what we do in the short term, but obviously this is not ideal, since we will now need to maintain an additional field whenever we are doing updates/inserts, etc.
Appreciate your responses, and look forward to working with you some more in the future!