durcno@1.0.0-alpha.4

Minor Changes

• a7442fe - Thanks to @almahdi404 !

  feat(migration/ddl): add type DDL API and split ddl module into files

  Introduced a new generic type DDL API to replace the old enum-specific helpers. The old methods (createEnum, dropEnum, alterEnumAddValue) are still available but now marked @deprecated.

  New API:

  // Create a PostgreSQL enum type
  ddl.createType("public", "user_type", { asEnum: ["admin", "user"] });
  
  // Drop a type
  ddl.dropType("public", "user_type");
  
  // Alter a type — fluent chainable builder
  ddl
    .alterType("public", "user_type")
    .addValue("moderator", { after: "admin" })
    .renameValue("guest", "visitor");

  alterType introduces a new renameValue capability that was not available in the old API.

  The src/migration/ddl/ module was also refactored from a single monolithic file into focused modules (enum.ts, indexes.ts, schema.ts, sequence.ts, statement.ts, table.ts, types.ts, utils.ts) with a re-exporting index.ts. This is a purely internal restructuring with no public API changes.

  The migration generator (durcno generate) now emits the new type API in freshly generated migration files.

Patch Changes

• 05ebbad - Thanks to @almahdi404 !

  fix(connectors/pglite): run migrations without transactions for pglite

  PGlite does not support DDL statements inside transactions and requires sequential execution. Previously, the generate command always emitted migration files with transaction: true, which caused migrations to fail silently or error out when using the PGlite connector.

  PgLiteConnector now declares a static migrationOptions override on the base Connector class:

  class PgLiteConnector extends Connector {
    ...
    static override migrationOptions = {
      transaction: false,
      execution: "sequential" as const,
    };
    ...
  }

  The generate command reads connector.migrationOptions and passes those values through generateMigration / generateNoOpMigration so that the emitted options export in up.ts and down.ts reflects the connector's requirements automatically — no manual edits needed.

• 6373d04 - Thanks to @almahdi404 !

  fix(cli/migration): combine transaction statements into single query for joined execution

  Previously, even in joined execution mode, BEGIN and COMMIT were issued as separate client.query() calls around the batched SQL. This meant three round-trips to the database instead of one.

  The fix embeds BEGIN; and COMMIT; directly into the single SQL string sent for joined execution, reducing it to a single round-trip and making joined migrations significantly faster.

  For sequential execution the behavior is unchanged: BEGIN/COMMIT are still sent as individual queries between each statement. The ROLLBACK on error is also now correctly scoped to sequential mode only, since a failed joined query is already rolled back by the database.