48 results found
-
Realtime Query Updates
Subscribe to realtime updates for a limited subset of queries, for example retrieving updates to specific rows or getting new items for a simple timeline.
235 votes -
Event Triggers
Trigger a Cloud Function when data in a table type is created (via insert or upsert), updated (via update or upsert), or deleted.
146 votes -
Cloud Firestore Datasource
Support Cloud Firestore as a datasource for Data Connect in addition to Cloud SQL. Support data model mapping (e.g.
@collection) and querying via GraphQL111 votes -
Add GraphQL enum support
Add support for the GraphQL enum type in @table types.
24 votes -
SQL Full-Text Search
Index and query your data with full-text search leveraging PostgreSQL's built-in capabilities including stemming, ignoring stop words, and weighted relevance scoring.
105 votes -
Offline Support
Allow data to be cached and accessible offline. Offline data may have limited query and write capabilities compared to online data
97 votes -
Support fetching/returning data from mutations
Currently mutations return only the primary key of the created record, but it would be nice to be able to fetch the full record (including e.g. defaulted values) as part of a mutation.
28 votes -
SQL Aggregation Queries in GraphQL
Support aggregations (COUNT, SUM, AVG, MIN, MAX) with grouping as part of the built-in GraphQL query builder.
48 votes -
How connect DBeaver in localhost database?
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 DBeaver2 votes -
More tutorial on data connect
We need more tutorial or documentation with examples.
8 votes -
Support geographic area and proximity searches with PostGIS
Add GeoPoint and GeoBox scalar types and enable rich geo searching queries including indexing, "search within area", "find closest to point within radius", etc.
15 votes -
Field Validation
Allow validation (e.g. min/max values, length, regex match) with custom error messages on both fields and variables. Enforce validation server-side but also provide client-side validation of variables for generated SDKs.
24 votes -
Custom Serverless Resolvers
Write Node.js resolvers to enhance Data Connect with arbitrary server logic. Resolvers will be authored alongside the Data Connect schema and deployed to serverless infrastructure. Resolvers can either provide new top-level Query and Mutation fields or integrate with SQL table types.
24 votes -
Integrate with Row Level Security (RLS)
Allow clear integration with Postgres's RLS while defining access permissions.
21 votes -
Low-Latency Data Cache
Allow configurable caching of query results for reduced end-to-end latency and reduced resource pressure on underlying data sources.
21 votes -
Allow to use customClaims in eq_expr
Im developing a multi tenant system using firebase dataconnect and it would be very usefull use a query like this:
query getServices @auth(level: USER) {
services(where: {
tenantId: {eq_expr: "auth.token.tenantId"}
})
{
id
name
}
}unfurtunately when i run this query i received the message:
query, getServices, services (where.tenantId.eqexpr: StringExpr): unsupported expression "auth.token.tenantId" (currently only "auth.uid" and "uuidV4()" are supported)3 votes -
Schema Creator Tool in the Firebase Console
Support creating GraphQL schema in the Firebase console
18 votes -
Allow to connect emulator with a tier SQL client
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.
1 vote -
Connectors with Admin-Only Access
Create sets of reusable operations that are not accessible from client applications but can be called from server code or manually in the Firebase Console.
16 votes -
Support inline/embeded types stored as structured JSONB columns
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
}10 votes
- Don't see your idea?