Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

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

77 results found

  1. Do something better in future before that I need to learn something about this 😞

    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

    1 comment  ·  Data Connect  ·  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. There is not documentation on how to connect Data Connect service to a Cloud SQL instance with Private IP. Deployment simply fails with timeout error.
    Had to open a support case to learn that I have to run the deployment command from within the same VPC. This should be at least documented. The deployment script could be improved, so that you don't have to run the deployment from a VM. The steps that are failing should be executed from the service directly, we'd just need to grant the required permissions to the SA.

    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  ·  Data Connect  ·  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. Hi Firebase Data Connect team,
    I’m currently using Firebase Data Connect with Cloud SQL (PostgreSQL) and facing a limitation related to foreign key delete constraints.
    PostgreSQL natively supports ON DELETE RESTRICT, and when I manually apply this constraint directly in Cloud SQL, everything works perfectly and the application behaves exactly as intended.
    However, Data Connect does not provide any way to define or preserve ON DELETE RESTRICT in its schema. While Data Connect does expose an explicit directive (the ! notation) to define ON DELETE CASCADE, there is no equivalent option for RESTRICT or other delete behaviors.
    Because of this,…

    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

    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  ·  Data Connect  ·  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. Add a directive to create a materialized view similar to the existing @view directive. This enables precomputation and storage of expensive query results, improving performance for frequently accessed or computationally intensive queries.

    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  ·  Data Connect  ·  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. Add extensions to allow querying by location radius. This is important for making apps especially social apps.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. One of the great things about firebase is that it didn't burden you of your design decisions and let you pay for resources when you needed it. Serverless is one of the main selling point of firebase, you can see its footprints on firestore, realtimedb, and firebase functions.

    Seeing the need to instantiate a DB instance when getting started with data connect was so disappointing for me because I thought it was a step in the wrong direction.

    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  ·  Data Connect  ·  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. Currently, the Firebase Emulator Suite allows running only a single Data Connect service instance locally. For projects utilizing a microservices architecture with multiple isolated Data Connect services, this creates a significant blocking issue during development.

    Primary Feature Request: Multi-Service Emulation - Please update the Emulator Suite to support running multiple Data Connect services simultaneously.

    Alternative / Interim Solution: Hybrid Cloud Fallback - If full multi-service emulation is technically complex to implement immediately, please introduce a "Hybrid" mode as an alternative.

    Current Behavior: When the emulator is running, all calls to Data Connect are forced to look locally. If a specific…

    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  ·  Data Connect  ·  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. Support Data Connect Event Triggers on emulator for local development. With the risk outlined in the event trigger documentation regarding infinite loops, we ought to be able to test our event triggers on emulator. Data Connect supports great local development except for the triggers, so this would be top notch!

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Provide better transaction open source database options like Postgres with Neon or MariaDB and optimized the Gemini model to interact with database to read and write schemas.

    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  ·  Data Connect  ·  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. In additional to the onMutationExecuted, we would love to have events on table mutations.

    • onRowUpdated
    • onRowCreated
    • onRowDeleted

    onMutationExecuted is already launched in Nov 2026. https://firebase.blog/posts/2025/11/dataconnect-nov25

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Firebase should publish a Gradle plugin for Data Connect Android development. The plugin could integrate the code generation into the build process, much like https://github.com/google/protobuf-gradle-plugin.

    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  ·  Data Connect  ·  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. 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  ·  Data Connect  ·  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. How about making a system out of structural foundation and can process it

    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

    1 comment  ·  Data Connect  ·  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. Provide order by option that moves nulls to the end of results per postgresql docs NULLS LAST (https://www.postgresql.org/docs/current/queries-order.html#QUERIES-ORDER)

    Nulls are last for ASC sorts by default, so it's only needed for DESC, so I'd propose adding a new DESC_NULLS_LAST prop to the OrderDirection enum (https://firebase.google.com/docs/reference/data-connect/gql/enum#OrderDirection)

    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  ·  Data Connect  ·  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. To generate voices

    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

    2 comments  ·  Data Connect  ·  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. First of all, thank you so much for the new Full-text Search feature! :)
    In our team, we would really love the following more advanced features, if possible, related to it:
    - Fuzzy matching: it would allow searches to be resilient to common typos and misspellings.
    - Prefix matching: it would enable users to find words that start with a specific string of characters, such as "invoic" returning "invoice," "invoices," and "invoicing."
    - Column-Specific Search: Instead of searching across all marked "searchable" columns, I would like to choose to focus a specific query on a specific subset. This would be…

    9 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Currently, any gql files placed in schema folder generate one FDC schema in FDC console, which generates associated tables in postgres PUBLIC schema. Putting tables there is not ideal.

    It would be nice if creating additional subfolders within schema source folder (or some other mechanism) could allow mapping to developer defined postgres schemas other than PUBLIC. For example, the following folder structure:

    schema/appname/*.gql

    would map to APPNAME schema in Postgres and tables would be created there.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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  ·  Data Connect  ·  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. Digi

    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

    2 comments  ·  Data Connect  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4
  • Don't see your idea?