durcno@1.0.0-alpha.2

Minor Changes

• 6be1ac2 - Thanks to @almahdi404 !

  impr(columns)!: add sqlCastScalar for prepared statement type casting

  Introduces a new abstract sqlCastScalar getter on the Column base class. Each column type returns either a PostgreSQL type string (e.g. "uuid", "boolean", "jsonb") or null when PostgreSQL can infer the type without an explicit cast (e.g. integer, varchar, text).

  A derived sqlCast getter on Column composes sqlCastScalar with array dimension suffixes automatically, matching the existing sqlType pattern.

  toSQL() and the internal #toSQLArray() now accept an optional { cast?: boolean } option. When cast: true is passed the generated SQL literal is suffixed with ::type, ensuring cases where PostgreSQL cannot infer the type are handled correctly.

  Arg (used by prepared statements) now stores the sqlCast from the column that produced it. Query.addArg() appends ::type automatically, and a new Query.pushArg() helper is provided for ad-hoc use.

  InsertReturningQuery now delegates to InsertQuery.toQuery() instead of duplicating the SQL-building logic, eliminating a class of divergence bugs.

  UpdateQuery's SET clause is simplified: both prepare and non-prepare modes now use toSQL(..., { cast: true }) inline, removing the branching that previously forced literal SQL in prepare mode.

  All built-in column types now implement sqlCastScalar.

  Custom column authors must add sqlCastScalar to any Column subclass:

  get sqlCastScalar(): string | null {
    return "citext"; // return null if PostgreSQL can infer the type
  }

Patch Changes

• 3217c70 - Thanks to @almahdi404 !

  fix(migration/fk): detect and generate FK reference changes

  The migration generator now detects when a column's foreign key references changes between schema snapshots and emits the appropriate ALTER TABLE statements.

  Two new actions are added to AlterTableBuilder: addForeignKey and dropForeignKey. When a column gains a reference, an ADD CONSTRAINT ... FOREIGN KEY statement is emitted. When a reference is removed, the corresponding DROP CONSTRAINT statement is emitted. If the reference target changes, a drop is followed by an add.

  // Generated migration when a FK is added to an existing column
  alterTable("public", "posts").addForeignKey("posts_user_id_fkey", "user_id", {
    schema: "public",
    table: "users",
    column: "id",
    onDelete: "CASCADE",
  });
  
  // Generated migration when a FK is removed from a column
  alterTable("public", "posts").dropForeignKey("posts_user_id_fkey", "user_id");

• 447fb69 - Thanks to @almahdi404 !

  fix(rq): throw clear error when relation column missing .references()

  When using many, one, or fk in a relations() definition, the relation column must call .references() to declare the join target. If .references() was omitted, the relational query (db.query(...).findMany(...)) would crash with a cryptic runtime error.

  Now a clear Error is thrown with a message that identifies the offending column and tells you exactly what to fix.

• 32d8cb6 - Thanks to @almahdi404 !

  refac(cli): replace require with dynamic import

  Replaced all synchronous require() calls in the CLI with await import() to use native ESM dynamic imports.

  getSetup in src/cli/helpers.ts is now async, and all CLI commands (down, generate, shell, squash, status) have been updated to await it.

  Migration module loading in generate and squash commands was also migrated from require() to await import().

• 204fab8 - Thanks to @almahdi404 !

  change(cli): remove type:module setup from init

  The init command no longer sets "type": "module" in their package.json, and the setTypeModule() helper has been removed entirely.

  This step was removed because Durcno no longer loads ESModule TypeScript files using require(). As a result, "type": "module" is no longer a requirement imposed by Durcno, and setting it during init is no longer necessary.