77 results found
-
Firestore : Throw error access data with offline cache without enable persistence
When retrieving documents from Firebase's Firestore on the web, if you attempt to read the value from the cache, it will return an empty result.
This seems to be an issue because Firestore's database does not use offline data when accessed from the web by default.
To make developers aware of this, should throw some error if Firestore's database is set to not use offline data, and attempting to read the cache value.
2 votes -
Duplicate document in collection in Firestore
Duplicate document in collection in Firestore
2 votes -
Support deleting collections in the API
Currently you can only delete collections programmatically via the CLI. Otherwise, you have to list and delete every single document in the collection. If those documents have nested collections, you have to (recursively) retrieve and delete every document in the nested collection (As deleting a document does not delete any nested collections the document has). If there are additional levels of nested collections... You get the idea.
I wasn't sure what this other request was referring to so I made this one: https://firebase.uservoice.com/forums/948424-general/suggestions/46562317-api-support-for-deleting-directories
3 votes -
25 votes
-
Firestore insights dashboard
Same dashboard in GCP as Firestore in datastore mode. Collection storage space usage, index size, data size, etc.
Also, for multi tenancy apps in both modes (using subcollections or multiple databases or also schemas in native mode would be nice to have) an API that can tell how much resources - space, reads, writes, etc. did each customer use, to be able to offer some kind of pay-as-you-go type of subscription.
6 votes -
Join collections in real-time (similar to lookup in mongodb)
The ability to join collections in real-time really allows developers to build complex use cases. Currently, I am having to denormalize data so excessively that the solution doesn't seem to scale. Having to implement workaround after workaround to circumvent the limitations.
An aggregate lookup function similar to that of mongodb would really be a life save. We are ok to compromise on the extra reads, and some performance if it means to bring us data consistency.
Really having this feature would stop people looking into RDBMS based alternative such as Supabase.
5 votes -
22 votes
-
Add Creator User UID to the Collection Record Metadata
Will allow further security validation and early detection of security checks failures.
To give an example of why this is important,
I use a Firebase Collection as an API alternative, I create a task record that triggers a cloud function, it allows me to manage my resources effectively and provide partial updates, way more flexible than traditional REST, however with API I use bearer tokens to verify that the identity of the person creating the record and deciding if they are allowed or 401, without UID in record metadata I have to send the plain UID as a field in…2 votes -
Firestore hosting in South Africa
Make Firestore and Firebase hosting available on the new Johannesburg Cloud Region; this will greatly assist developers in launching apps within the continent and also assist with local data protection regulations.
2 votes -
Raise the Firestore Rules Expression Limit
Raise the maximum expression limit for firestore rules to make more complex doc schema validation possible.
1 vote -
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.
8 votes -
Move documents and collections to a new location
Instead of making us create inefficient solutions/workarounds ourselves, it would be nice if a convenient API was provided for this functionality.
For example, transfer
col1/doc1/col2
and all its children tocol1/doc2/col2
8 votes -
Encrypted Collections in Firestore
Ability to mark certain collections to be Encrypted so it's not readable even in the firebase console.
There are some application types that require this sort of behaviour to increase security.
Say you are building a messaging app, you would not want the messages between your users to be seen on the console.
4 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.
15 votes -
Transactions should allow exponential backoff retries like pub sub
Transactions allow passing an options object with maxRetries, but all retries are immediate. If there are many other functions writing the same document, transactions will fail after all retries (lock will time out). Maybe a better strategy would be to delay with exponential backoff like pub sub does.
1 vote -
custom gpt to firestore
I wanted to create my own GPT using OpenAI's new GPT builder which has "Functions" in it, and I wanted it to be able to use Firestore API to perform CRUD operations, but unfortunately I struggled to find documentation on how to do that.
1 vote -
Allow developers to use the local Firestore database for free
It'd be really nice if you could allow users to create local drafts, of small documents, for instance, and save them locally for free with Firestore.
This way you wouldn't have to coordinate Firestore and its rules with some other database and client code nor would you have to choose the simpler option of getting charged for writes and reads on remote database documents that really only one user is supposed to write and read.
Please note that while you could use the realtime database to save drafts, 1 it's not always easy to figure out whether that'd actually be…
1 vote -
Support offset-based document access and pagination
There should be an easy way to get a specific document by index in a query:
// this query should work as it's read, if i wanted to use gte i'd use a where
query(this.collection, orderBy('anything', 'asc'), startAt(index), limit(1))
1 vote -
firestore 'in' 2d array order optional
For some reason an 'in' wury with a 2d array also runs with a sort function. which is not provided or supported by other features such as ArrayUnion and ArrayRemove.
the order should be an optional parameter because using a system where we must find all other documents that have the exact same features but maybe in a different order, is not possible. there is no native sort option when using ArrayUnion, and we've been taught through firestore arrays in general, that orders of items fundamentally shouldn't be considered to exist due to idempotency.
TLDR:
ArrayUnion does not support 'in…1 vote -
17 votes
- Don't see your idea?