Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Use Markdown for this comment
Set severity, which reflects how much the issue affects the use of the product
Assign issue to yourself
Pending code changes (auto-populated)
[ID: 82937]
Primary programming language affected, if applicable [ID: 82936]
[ID: 82935]
[ID: 82940]
[ID: 82941]
Set the version(s) of the product affected by this issue (comma-separated list)
Set the version(s) of the product in which the issue should be fixed (comma-separated list)
Set the version(s) of the product in which the issue fix was verified (comma-separated list)
Set if this issue occurs in production
Set Reporter
Set Type
Set priority, which reflects how soon the issue should be fixed
Set Status
Set Assignee
Set Verifier
Remove item
View or edit staffing
View issue level access limits(Press Alt + Right arrow for more information)
Description
This will create a feature request which anybody can view and comment on.
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish: Customer would like to have the capability to perform case-insensitive queries by string property value. Currently, Firestore's EQUAL operator only returns entity/documents where the property values match exactly with the value from the query.
How this might work: Customers will be able to use case insensitive while filtering documents with specific fields
If applicable, reasons why alternative solutions are not sufficient: To accomplish the equivalent in Firestore, one would have to create a separate property to store the normalized value of the property, and maintain the normalized property during subsequent updates of the non-normalized property of a document.
mongoDB supports Case Insensitive Indexes, where queries can lookup documents with matching properties regardless of case. A similar feature would allow fast document lookup (without having to scan the entire index) while tolerating case mismatches in the query.
Other information (workarounds you have tried, documentation consulted, etc):
To support case-insensitive or any other canonicalization you'll need to write a separate field that contains the canonicalized version and query against that. For example
I also found this good explanation from Stackoverflow, they mentioned that the only way to achieve your use-case is to store the field twice, please go through this link that explains how to achieve this.