113 results found
-
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.
7 votes -
structure and organization of Firestore collections: documentation
Normally documentation about collections is done in a 3rd party tool like notion, jira, google docs (or notepad for the brave ones).
After a while this easily becomes inconsistent due to ongoing changes throughout the project development. The same way as we document code directly in the code file, it'd be great to document collections directly in the firestore console.
For this, something simple like a text input would suffice (ideally with some minimal markdown, but not mandatory). If developers need to add more detailed info or explanations (and make use of charts, designs, videos, whatever) they could simply add…
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.
2 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.
11 votes -
The ability too see when an index was last accessed
When a project grows to a certain size, you'll likely have many indexes with associated queries.
However, queries change, or get removed, and currently there's no way to see if an index could be safely removed, after a query is; which would be a great feature.
11 votes -
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…
20 votes -
24 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.
5 votes -
24 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.
18 votes -
Improve performance & speed of client side write
I've used both Firestore and MongoDB's Realm Device Sync. While Firestore works great in terms of scaling, the performance and speed for client side write is far behind realm, especially when client side is doing some batch writes.
Realm uses techniques like data compression and delta sync to reduce the data size when uploading (https://www.mongodb.com/docs/atlas/app-services/sync/details/protocol/), I'd like to see Firestore doing the same and improve the performance of client side batch write.
Also, what I've noticed is that Firestore's client side write performance degrades a lot after some time being offline, this isn't great for apps that would…
9 votes -
Support offline capabilities for mobile using React Native
I can see offline capabilities for mobile using Kotlin, Java, Swift and Objective-C. I am requesting offline support for React Native application.
1 vote -
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 -
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/col2and all its children tocol1/doc2/col28 votes -
Create way to duplicate documents within firebase console so we can easily move them elsewhere
Sometimes it would be nice to have ability to use the console to Duplicate/Copy firestore documents and put them in different locations of the database.
4 votes -
Add option to save a query in Firestore Query Builder
I have some queries that I perform frequently through Firestore Query Builder. It would be great to save queries to be able to run them with one click.
3 votes -
It's impossible to import data into the emulator without first exporting, which is a backwards design
Developers should be able to use the CLI to easily pass in a path to a json file, whose contents may be imported into a firestore emulator collection. For instance:
firebase emulators:start --import ./data/import.json --collection=puzzles
4 votes -
Provide a way to document and share models across platforms.
Afaik there is currently no standard way to a) document the structure and organization of Firestore collections and documents stored in a project expected by apps which use it, and b) share the model definition across languages and platforms. Instead, each client requires its own implementation of the app-specific model and conversion to/from Firestore's model which needs to be kept up-to-date as the system involves.
If there were a way to share this model (for ex. proto, JSON schema, other) and easily use it from Firestore APIs, it would reduce dev and maintenance cost and improve developer experience.
3 votes
- Don't see your idea?