firebase-contract 0.1.0-rc.8 → 0.1.0-rc.9

package/README.md

@@ -590,7 +590,7 @@ project:
 | `api-validation`         | api | `api-validation.ts`           | endpoint request-validation Zod                        |
 | `api-dto`                | api | `<operation>.dto.ts` per api  | class-validator DTO classes (NestJS `dto/` convention) |
 | `task-payloads`          | api | `task-payloads.ts`            | envelopes + `*TaskData`/`*TaskPayload` + constants     |
-| `sql-migrations`         | document | `migrations/constraints.sql`  | composite FK / CHECK / index SQL                       |
+| `sql-migrations`         | document | `migrations/constraints.sql`  | composite FK / CHECK / index SQL — idempotent (`IF NOT EXISTS` / `duplicate_object` guard), safe to re-apply whole |
 | `id-codecs`              | document | `id-codecs.ts` (+ `id-core.ts`) | typed per-entity id encode/decode wrappers; emits the Sqids primitives when `project.idCodec` is set |
 | `unions`                 | document | `unions.ts`                   | Zod discriminated unions + TS union types              |
 | `config`                 | document | `dataconnect.yaml`, `connector.yaml`, `constants.ts` | DC configs + sync constants (preview — see [Project config](#project-config)) |

package/dist/lib/_internal/generators/sql/sql-migration-generator.d.ts

@@ -3,7 +3,8 @@ import { Generator } from '../generator.js';
  * Generates raw SQL migrations for constraints Data Connect cannot express:
  * composite foreign keys, CHECK constraints, and extra indexes — constraints
  * that otherwise live only as hand-written schema comments with no executable
- * artifact. This turns them into a runnable `.sql` file.
+ * artifact. Every statement is idempotent (`IF NOT EXISTS` / duplicate_object
+ * guard), so the whole file can be (re)applied to any environment safely.
  */
 export declare const createSqlMigrationGenerator: () => Generator;
 //# sourceMappingURL=sql-migration-generator.d.ts.map

package/dist/lib/_internal/generators/sql/sql-migration-generator.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"sql-migration-generator.d.ts","sourceRoot":"","sources":["../../../../../src/lib/_internal/generators/sql/sql-migration-generator.ts"],"names":[],"mappings":"AAEA,OAAO,EAAiB,SAAS,EAAoB,MAAM,iBAAiB,CAAA;AAgC5E;;;;;GAKG;AACH,eAAO,MAAM,2BAA2B,QAAO,SAY7C,CAAA"}
+{"version":3,"file":"sql-migration-generator.d.ts","sourceRoot":"","sources":["../../../../../src/lib/_internal/generators/sql/sql-migration-generator.ts"],"names":[],"mappings":"AAEA,OAAO,EAAiB,SAAS,EAAoB,MAAM,iBAAiB,CAAA;AA0C5E;;;;;;GAMG;AACH,eAAO,MAAM,2BAA2B,QAAO,SAY7C,CAAA"}

package/dist/lib/_internal/generators/sql/sql-migration-generator.js

@@ -2,6 +2,12 @@ import { pluralize, snakeCase } from '../support/naming.js';
 import { headerBlocks } from '../support/header.js';
 import { outputFile } from '../support/templates.js';
 const tableName = (model) => model.table ?? pluralize(snakeCase(model.name));
+/**
+ * Postgres has no `ADD CONSTRAINT IF NOT EXISTS`, so constraint statements are
+ * wrapped in a DO block that swallows `duplicate_object` — rerunning the whole
+ * file against an already-migrated database is a no-op.
+ */
+const guarded = (statement) => ['DO $$ BEGIN', `  ${statement}`, 'EXCEPTION WHEN duplicate_object THEN NULL;', 'END $$;'].join('\n');
 const renderModelSql = (model) => {
     const sql = model.sql;
     if (!sql)
@@ -10,17 +16,17 @@ const renderModelSql = (model) => {
     const statements = [];
     sql.checks.forEach((expr, i) => {
         const name = `${table}_chk_${i + 1}`;
-        statements.push(`ALTER TABLE "${table}" ADD CONSTRAINT "${name}" CHECK (${expr});`);
+        statements.push(guarded(`ALTER TABLE "${table}" ADD CONSTRAINT "${name}" CHECK (${expr});`));
     });
     for (const fk of sql.foreignKeys) {
         const name = fk.name ?? `${table}_${fk.columns.join('_')}_fkey`;
         const cols = fk.columns.map(c => `"${c}"`).join(', ');
-        statements.push(`ALTER TABLE "${table}" ADD CONSTRAINT "${name}" FOREIGN KEY (${cols}) REFERENCES ${fk.references};`);
+        statements.push(guarded(`ALTER TABLE "${table}" ADD CONSTRAINT "${name}" FOREIGN KEY (${cols}) REFERENCES ${fk.references};`));
     }
     for (const idx of sql.indexes) {
         const name = idx.name ?? `${table}_${idx.columns.join('_')}_${idx.unique ? 'uidx' : 'idx'}`;
         const cols = idx.columns.map(c => `"${c}"`).join(', ');
-        statements.push(`CREATE ${idx.unique ? 'UNIQUE ' : ''}INDEX "${name}" ON "${table}" (${cols});`);
+        statements.push(`CREATE ${idx.unique ? 'UNIQUE ' : ''}INDEX IF NOT EXISTS "${name}" ON "${table}" (${cols});`);
     }
     return statements.length > 0 ? [`-- ${model.name} (${table})`, ...statements] : [];
 };
@@ -28,7 +34,8 @@ const renderModelSql = (model) => {
  * Generates raw SQL migrations for constraints Data Connect cannot express:
  * composite foreign keys, CHECK constraints, and extra indexes — constraints
  * that otherwise live only as hand-written schema comments with no executable
- * artifact. This turns them into a runnable `.sql` file.
+ * artifact. Every statement is idempotent (`IF NOT EXISTS` / duplicate_object
+ * guard), so the whole file can be (re)applied to any environment safely.
  */
 export const createSqlMigrationGenerator = () => ({
     name: 'sql-migrations',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "firebase-contract",
-  "version": "0.1.0-rc.8",
+  "version": "0.1.0-rc.9",
   "type": "module",
   "bin": {
     "firebase-contract": "./dist/lib/cli/index.js",