74 results found
-
Connect to an existing instance of another project
Allow connections to PostgresSQL instances in other projects using Shared VPC, etc.
14 votes -
Postgres Functions exposed as an API
Similar services, like postgraphile, allow exposing queries / mutations as postgres functions. It's extremely powerful, and allow extremely custom queries / logic for exposing data to the clients.
13 votes -
Data connect support for Postgres instances outside Google Cloud
It would be nice if we can set our custom Postgres instance connection string so that we can use postgres instances outside the Google Cloud infrastructure.
10 votes -
Support for data connect in the Python Firebase admin SDK
A lot of our Firebase functions are written in Python. It would be useful to have the ability to use Data Connect in these functions too.
9 votes -
AlloyDB Datasource
Support AlloyDB as a datasource for Data Connect in addition to Cloud SQL via the same PostgreSQL bindings
9 votes -
Advanced Vector Embeddings with pgvector
Create and store advanced embeddings for Data Connect types in pgvector through support of configurable chunking strategies and automatic embedding by annotations.
9 votes -
Data connect Full-text Search
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…8 votes -
Custom GraphQL Scalar Support
On top of common scalars such as Email, Phone, etc., custom scalars are defined by developers on the client-side application, with logic for marshaling and unmarshalling the data provided, which could be either a class with the two methods or a couple of functions.
8 votes -
Data Transformation With CEL expression
I love that data connect supports
{.._expr: "auth.uid"}to define server value based on Firebase auth token.What about other CEL operations?
I want the ability to perform simple transformation using GraphQL variables, Firebase auth token and current timestamp. For example:
_expr: "'hello from ' + auth.email"I want the ability to combine data from different sources. Like execute a query and then use its result to perform another query or mutation. CEL expression can help cross reference data in previous steps.
8 votes -
Vertex AI Integration
Add deeper integration with Vertex AI to Data Connect, for example allowing direct LLM content generation and simple RAG use cases.
8 votes -
7 votes
-
Data Connect Event Triggers on Emulator
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 -
Enhanced Foreign Key Behavior
I am reaching out to share a suggestion regarding the current implementation of foreign key constraints in Firebase DataConnect.
Currently, it appears that the default behavior for foreign keys is automatically assigned during schema deployment, and there is no way to explicitly define ON DELETE and ON UPDATE rules (e.g., NO ACTION, CASCADE) in the GraphQL schema. This limitation has the following implications:
1. Deployment Overrides: Even if these rules are manually adjusted in the underlying PostgreSQL database, deploying an updated schema resets the rules to the platform’s defaults.
2. Lack of Customization in Schema: Adding support for directives like…5 votes -
Using Genkit embedders (including from e.g. genkitx-openai-plugin)
Instead of only being able to select embedding models from Vertex AI (e.g. Gecko), it'd be great to be able to pass in any embedder imported from Genkit plugins like genkitx-openai-plugin or genkitx-cohere
5 votes -
Cloud Spanner Datasource
Support Cloud Spanner as a datasource for Data Connect in addition to Cloud SQL via Cloud Spanner's PostgreSQL compatibility layer.
5 votes -
Map Firebase Data Connect (FDC) schema to custom postgres schema (not PUBLIC)
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 -
Sending arrays as parameters, to allow scaling.
When building simple select queries in GraphQL (really simple ones), the underlying query is being transformed, sending the values through as parameters.
As you can use arrays as parameters, that would allow the DBs to scale as it makes this more robust. Without scaling, it will limit production applications form fully investing.
As an example you run into instances where the select for 50 columns in the schema (a standard employment record, nothing special) is transformed and we end up getting the dreaded 100 parameters error. This is a Postgres issue, but can be avoided.
The Error for the fun…
4 votes -
Geo Querying in Data Connect
Add extensions to allow querying by location radius. This is important for making apps especially social apps.
3 votes -
Table Event Triggers
In additional to the
onMutationExecuted, we would love to have events on table mutations.onRowUpdatedonRowCreatedonRowDeleted
onMutationExecutedis already launched in Nov 2026. https://firebase.blog/posts/2025/11/dataconnect-nov253 votes -
Aggregation Order by Value
With data connect aggregation queries, I would like to order the returned results by an aggregated value. The below example fails with the message: "Field "count" is not defined by type "LeadOrder". Did you mean ...?"
query {
leads(orderBy: [{ _count: DESC }], limit: 10) {
company
_count
}
}3 votes
- Don't see your idea?