Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

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

54 results found

  1. Add an argument to the @unique annotation that allows users to choose between using PostgreSQL's "UNIQUE NULLS NOT DISTINCT" constraint or the standard "UNIQUE" constraint when defining a unique constraint.

    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)
  2. 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…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Allow connections to PostgresSQL instances in other projects using Shared VPC, etc.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Support AlloyDB as a datasource for Data Connect in addition to Cloud SQL via the same PostgreSQL bindings

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Create and store advanced embeddings for Data Connect types in pgvector through support of configurable chunking strategies and automatic embedding by annotations.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    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)
  9. Support Cloud Spanner as a datasource for Data Connect in addition to Cloud SQL via Cloud Spanner's PostgreSQL compatibility layer.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Add deeper integration with Vertex AI to Data Connect, for example allowing direct LLM content generation and simple RAG use cases.

    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)
  11. 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

    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. 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. Currently only PostgreSQL is supported, but we are also highly interested in mysql support. Would love to see it on the roadmap.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 3 Next →
  • Don't see your idea?