52 results found
-
190 votes
-
Automatic Backups for Firestore
This feedback has been automatically imported from Firebase's Bug Tracker.
164 votesScheduled Backups for Firestore is now in public preview:
-
80 votes
-
Search collections in Firestore by field values
Ability to search collections and documents in the Firestore UI.
54 votes -
52 votes
-
51 votes
-
Support multiple range query
We would like to narrow down the range so that it can be divided and synchronized, but it is not enough if there is only one range condition.
It would be great if we could narrow down it by two conditions by adding at least one more range.For example,
* TimeRange & IntRange
At Some EC services:createdAtbefore 1 month ANDprice> 5000- IntRange & IntRange
At Some graphic services: (500 >=
x> 0) AND (0 >=y> -500)createdAtbefore 1 month ANDprice> 5000
Query is like this:
collectionRef
.where("x", ">", 0).where("x",…39 votes - IntRange & IntRange
At Some graphic services: (500 >=
-
43 votes
-
26 votes
-
Request to Have a Firestore Profiler
Similar to RTDB, it would be good to have a way to monitor Firestore usage as it happens. There are many reads happening that I would like to better understand the source of.
23 votes -
DocumentReference join query
Please add a join query to Cloud Firestore. It seems that using DocumentReference for the join would be appropriate.
19 votes -
22 votes
-
20 votes
-
21 votes
-
Security Rules: unique() operator
I am submitting a feature request to introduce a 'unique()' operator in Firestore's security rules, offering a streamlined method to enforce data uniqueness within collections. This operator would not only simplify validation and potentially reduce reads by leveraging Firestore's hidden index table, but also eliminate the need for a separate cloud function, similar to the 'get()' and 'exists()' operations.
Background:
At present, ensuring data uniqueness in Firestore often requires workarounds that are less than optimal and can impact scalability.
Feature Proposal:
The proposed 'unique()' operator would operate much like the 'exists()' operation, but with a focus on reading Firestore's concealed…
7 votes -
Allow updating multiple documents through a query
Many other databases have support for update queries, such as:
- Apply "x" update data to all docs matching "y" query
- Delete all docs matching "x" query
Maybe these queries would only count as 1 write per doc, as opposed to 1 read + 1 write. At the very least they would have better performance.
13 votes -
17 votes
-
Allow field selections in client sdk's
Let's say I have an orders collection where each document represents a customer order.
I would like to be able to fetch and listen to only the names and dates of all orders and not get the whole document.
This would speed up a lot queries where not all fields are required and save bandwidth for users.
Since selection is already present in some server side SDK's I wonder if this could be enabled with a somewhat manageable effort.
7 votes -
How to reduce reads for static data
I want to ask documentation on how to reduce the number of unnecessary reads. eg. my product data
let query = store.collection("products");
Assuming I have 500 products, one user click on get products = 500 reads ? If 100 users click that function, then all my quota is gone in 1 minute. Is that right?
How can I overcome this.
Please provide a full example. I have seen Mr Duckworth's presentation in a firebase event, but could not see a good example.
1 vote -
FieldValue.min() and FieldValue.max()
Currently the Firestore API supports FieldValue.increment() to atomically increment or decrement a numeric value. I propose to add:
FieldValue.max(value): if the provided value is greater than the existing value on the server, then the field on the server takes this value. If it is less than the existing value, then the existing value remains.
FieldValue.min(value): (the opposite) if the provided value is less than the existing value on the server, then the field on the server takes this value. If it is greater than the existing value, then the existing value remains.
These operators should work on numeric fields AND…
12 votes
- Don't see your idea?