37 results found
-
Interfaces, Union types in GraphQL
Support for GraphQL Interfaces or Union Types through the built in GraphQL schema builder tool. This was extensively discussed in the Google Chat group.
6 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.
8 votes -
have a unity sdk for dataconnect
I'd like a Unity SDK for DataConnect
1 vote -
AlloyDB Datasource
Support AlloyDB as a datasource for Data Connect in addition to Cloud SQL via the same PostgreSQL bindings
7 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.
4 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.
5 votes -
More tutorial on data connect
We need more tutorial or documentation with examples.
1 vote -
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.
5 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.
3 votes -
4 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.
4 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.
3 votes -
1 vote
-
Support for MySQL
Currently only PostgreSQL is supported, but we are also highly interested in mysql support. Would love to see it on the roadmap.
2 votes -
Connect to an existing instance of another project
Allow connections to PostgresSQL instances in other projects using Shared VPC, etc.
2 votes -
Custom SQL Schema Migrations
The automatic custom schema migrations are great, but when managing an API expressed almost explicitly by the schema, there needs to be a clear dev story of how to migrate the database schema yourself, and move data in custom ways, while still allowing the exposed api to be backwards compatible. This can be very challenging with automatic migrations.
1 vote -
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
1 vote
- Don't see your idea?