durcno@1.0.0-alpha.13

Major Changes

• e09cdfe - Thanks to @almahdi404 !

  change(migration/ddl)!: remove deprecated enum DDL helpers

  Removed the deprecated enum-specific DDL helpers that were superseded by the generic type API in v1.0.0-alpha.4.

  Removed from ddl:

  • ddl.createEnum() → use ddl.createType(schema, name, { asEnum: [...] }) instead
  • ddl.alterEnumAddValue() → use ddl.alterType(schema, name).addValue(...) instead
  • ddl.dropEnum() → use ddl.dropType(schema, name) instead

  Removed classes (were re-exported from durcno/migration):

  • CreateEnumStatement
  • AlterEnumAddValueStatement
  • DropEnumStatement

  Removed from DDLStatementType: "createEnum", "alterEnum", "dropEnum".

• 093303c - Thanks to @almahdi404 !

  change!(insert): replace $insertReturning with returning("*")

  The db.$insertReturning() shortcut has been removed. Use .insert().values(...).returning("*") instead to insert a row and get back all columns including auto-generated values.

  returning("*") is a new overload on InsertQuery that emits RETURNING * and returns a fully-typed array of the inserted rows. It works for both single-row and multi-row inserts.

  // Before (removed)
  const user = await db.$insertReturning(Users, {
    username: "john",
    type: "user",
  });
  
  // After
  const [user] = await db
    .insert(Users)
    .values({ username: "john", type: "user" })
    .returning("*");
  
  console.log(user.id); // auto-generated ID
  console.log(user.createdAt); // auto-generated timestamp

Minor Changes

• afa2485 - Thanks to @almahdi404 !

  feat(query-builder): support bigint and Arg for limit/offset

  limit and offset in both db.from and db.query now accept bigint in addition to number.

  For prepared queries, limit and offset can be parameterized using the new Arg.number() and Arg.bigint() static factory methods on Arg. This enables paginated prepared statements where the page size and offset vary at runtime.

  const paginatedUsers = prequery(
    { lim: Arg.number(), off: Arg.number() },
    (args) =>
      db.prepare().from(Users).select().limit(args.lim).offset(args.off),
  );
  const page1 = await paginatedUsers.run(db, { lim: 10, off: 0 });
  const page2 = await paginatedUsers.run(db, { lim: 10, off: 10 });

  offset is also now supported inside nested many relation options in RelationQueryBuilder, matching the existing where, orderBy, and limit support.

• 49cf1ae - Thanks to @almahdi404 !

  feat(constraints): add column-level check constraints

  Adds support for defining CHECK constraints directly on column definitions using the new .check() method. This allows for more intuitive constraint definitions at the column level.

  Key Changes

  • Column.check(): New method to attach a CHECK constraint function to a column that receives the column and returns a filter or SQL expression
  • Type System Updates: Updated filter functions (arrayContains, arrayHas, etc.) and constraint types to accept both table columns and individual columns via the new AnyColumn type
  • CheckExpression Enhancement: The CheckExpression type now supports both TableAnyColumn and AnyColumn for greater flexibility

  Example

  export const Projects = table("public", "projects", {
    name: varchar({ length: 255 }).check((c) => gte(length(c), 5)),
    budget: integer().check((c) => gte(c, 1)),
  });

  This provides a cleaner, more declarative way to define column constraints compared to table-level constraint definitions.