Skip to content

General

General

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

81 results found

  1. Ability to select and copy fields and values in firestore document, more like making everything selectable text.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. We have unstructured data and each document can have different subcollections.
    We want to know get the names of all the subcollections present in a collection.

    Currently we have to iterate over all the documents present in a collection and for each document we are pulling the list of subcollections present in it.
    This process is very resource consuming and slow. We have to fire a query for each document present in the collection.

    Please provide an api something like db.collection("collectioName").listSubCollectionNames();

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. A RELATE statement to adds graph edges between records. Like the convention of vertex -> edge -> vertex or noun -> verb -> noun, enabling the addition of metadata to the edge record.

    Example: https://surrealdb.com/features#surrealql

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. You can build a search index in a Firestore collection by storing an array of search words.
    If you query this property using 'array_contains' you get exact matches for your search string.
    If you wish to build a prefix search, then you potentially need to store all prefixes of the words you need to index.

    Assuming that the array-contains is performing some kind of index scan, it would appear that it was possible to create an array-contains-prefix such that:

    where('index', 'array-contains-prefix', 'fire')
    would match the following documents

    [
    { index: ["firestore", "database"],
    ...
    },
    { index: ["firebase", "dog"],
    ...
    }

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Hello,
    is it possible to use signInWithCustomToken to authenticate in Python and retrieve documents from a collection?
    Does it work in Python only with cred = credentials.Certificate('serviceAccountKey.json')?

    Thanks

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. We've rules to limit access to data in both firestore and realtime database, but there are requirements where I need to specify a rule of realtime database based on a value in Firestore.

    Games are classical examples, I want to store the realtime game data in realtime DB but apply rules to read and write there based on my user and app data in firestore.

    Lack of this is either making me use either of the DB or write hard rules in client side (which is not really secure).

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Firestore automatically indexes all fields in all collections adding to storage size and slowing write performance.

    We can add single-field exemptions but we need to list all fields separately and there is a database-wide limit of 200 field exemptions.

    In a highly optimised use case we would want to index only specific fields that we know we query on, and just exclude all others.

    It's almost like the current behaviour is a database for novices, but we can't optimise for serious production.

    We need either a wildcard exclusion, or effectively just a switch/setting that says "only fields with explicit index…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. One frequent and strange bug we are facing with firestore is the dropping of events when designing large batch onWrite-listeners. This leads to unexpected bugs in production code.

    For some reason, when executing say 300 to 1000 onCreates at once, different events seem to drop and are never responded too.

    A way to access the tracelog of firestore events (in Stage 1 Cloud functions) would help us debug this problem. It would also help replay event streams in case the database is corrupted due to non-responding to the event streams.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Values which should be computed only when outputting data, can be stored as futures.

    Like https://surrealdb.com/features#datamodel

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. There's currently no way to get the collections existing in a document using the Unity SDK. ListCollectionsAsync exists in the .Net SDK.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Running quick queries straight from the console is currently impossible, making it hard to make adjustments DB wide without fiddling with code.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Imagine how cool it would be to have a debugger for my rules, where I can put breakpoints and see what exact data or condition is causing my rules to fail or pass.

    Often times I had to spend so much time in trial and error when writing complex rules for my application. If there is a debugger like I mentioned which is more like any other IDE, it would be super easy and a great developer experience.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. It has happened to me that I accidentally deleted some documents. While you can restore a collection from a backup, there is no option to not overwrite existing data.

    This unfortunately makes it impossible to restore accidentally deleted documents, without also affecting other documents that have changed since you last made that backup. The restore would undo lots of changes that happened after the backup was made.

    I think a very effective and simple solution could be to allow only injecting those documents from the backup that do not exist in de target collection. So no document is ever overwritten/updated…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?