Builds and deploys Firebase SQL Connect (aka Firebase Data Connect) backends with PostgreSQL securely. Use when designing schemas with tables and relations, writing authorized queries and mutations, configuring real-time data updates, or generating type-safe SDKs. Use when you need a relational database with Firebase, or when the user mentions SQL Connect or Data Connect.
Installation
Summary
Builds and deploys Firebase SQL Connect (aka Firebase Data Connect) backends with PostgreSQL securely. Use when designing schemas with tables and relations, writing authorized queries and mutations, configuring real-time data updates, or generating type-safe SDKs. Use when you need a relational database with Firebase, or when the user mentions SQL Connect or Data Connect.
Web (TypeScript): reference/sdkweb.md
Android (Kotlin): reference/sdkandroid.md
iOS (Swift): reference/sdkios.md
Admin (Node.js):
SKILL.md
Firebase SQL Connect
Firebase SQL Connect is a relational database service using Cloud SQL for
PostgreSQL with GraphQL schema, auto-generated queries/mutations, and type-safe
SDKs.
[!NOTE] Product Rename: Firebase Data Connect was renamed to Firebase
SQL Connect. All instructions, references, and examples in this skill
repository referring to "Data Connect" or "Firebase Data Connect" apply to
"SQL Connect" and "Firebase SQL Connect" as well.
Project Structure
dataconnect/
├── dataconnect.yaml # Service configuration
├── seed_data.gql # LOCAL ONLY — prototype/test data
├── schema/
│ └── schema.gql # Data model (types with @table)
└── connector/
├── connector.yaml # Connector config + SDK generation
├── queries.gql # Queries
└── mutations.gql # Mutations
Key Tools for Validation
Rely on these two mechanisms to ensure project correctness:
Review GraphQL Schema: Both user-defined and generated extensions (in
.dataconnect/schema/main/).
Validate Operations: Run
npx -y firebase-tools@latest dataconnect:compile against the schema.
Operation Strategies: GraphQL vs. Native SQL
Always default to Native GraphQL. Native SQL lacks type safety and
bypasses schema-enforced structures. Only use Native SQL when the user
explicitly requests it or when the task requires advanced database features.
Strategy
When to use
Implementation
Native GraphQL (Default)
Almost all use cases. Standard CRUD, basic filtering/sorting, simple relational joins. Requires full type safety.
Auto-generated fields (movie_insert, movies). Strong typing and schema enforcement.
Raw SQL string literals via _select, _execute, etc. Requires strict positional parameters ($1). No type safety.
Development Workflow
Follow this strict workflow to build your application. You must read the
linked reference files for each step to understand the syntax and available
features.
1. Define Data Model (schema/schema.gql)
Define your GraphQL types, tables, and relationships (which map to a Postgres
schema).