Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

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

61 results found

  1. How connect DBeaver in localhost database?
    I love DBeaver and i can connect in my production database but i cant connect in localhost database, always i try connect the firebase emulator give an generic error and crash.
    I can use the firebase dataconnect:sql:shell but is not so good like DBeaver

    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)
  2. I get that firebase dev really want to push their DataConnect api but any full featured tiers SQL client would allow us to have a wider view of what worked in our dev environment.

    It would be way faster than using any official cli or any generated query to look how our data is shaped within the database.

    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)
  3. Allow configurable caching of query results for reduced end-to-end latency and reduced resource pressure on underlying data sources.

    29 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)
  4. Support creating GraphQL schema in the Firebase console

    29 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)
  5. Hello me Rehan

    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. Allow storing structured types in JSONB columns using an @inline (or @embed) directive on the field.

    type Address {
    street: String!
    street2: String
    city: String!
    state: String!
    zipcode: String!
    }

    type User @table {
    address: Address @inline # stores as JSONB
    }

    19 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)
  7. 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. I need to have this SDK because for now only React and Angular have SDK.

    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)
  9. Given a schema with a nullable type

    type MyType @table() {
    id: uuid!
    nullableString: String
    }

    When running a query that selects records from MyType and filters out null values for nullableString, the generated SDK still types nullableString as string | null (or string? | null). Even though the query ensures no null values are returned for that field.

    It would be great if the SDK could be smarter and refine the generated type to just string when the query explicitly filters out null values for that field.

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

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

    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)
  12. Store and retrieve large files with Data Connect through an integration with Google Cloud Storage.

    22 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)
  13. Support federating a Data Connect service with other GraphQL schemas using federation protocols. Stitch together existing GraphQL services with Data Connect.

    17 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. One of the things that makes postgres great is it's extension support. Inability to integrate with extensions like postgis is a severe blocker.

    18 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)
  15. Data Connect automatically queues and applies database schema migrations as you make changes to your application's schema including destructive migration detection and diff approval.

    18 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)
  16. Support for GraphQL Interfaces or Union Types through the built in GraphQL schema builder tool. This was extensively discussed in the Google Chat group.

    13 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)
  17. Allow connections to PostgresSQL instances in other projects using Shared VPC, etc.

    14 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. 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)
  19. Postgres support jsonb column that can store arbitrary jsonb objects, very suitable to store unstructured / semi-structured API output.

    Postgres also supports index on fields within jsonb.

    Can data connect support jsonb column? Mapping fields of API object to Postgres columns can be a headache

    13 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)
  20. 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.

    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)
  • Don't see your idea?