durcno@1.0.0-alpha.11

Minor Changes

• 536cce6 - Thanks to @almahdi404 !

  fix(columns/validators): correct type inference for nullable columns in insert and update

  Fixed incorrect TypeScript type inference for nullable columns across ValTypeInsert, ValTypeUpdate, and ValTypeSelect in Column, as well as the Zod insert/update schema generators.

  ValTypeInsert now correctly marks nullable columns as ValType | Sql | null | undefined (optional with null), and notNull columns without a default as ValType | Sql (required, no null).

  ValTypeUpdate now consistently returns ValType | undefined for notNull columns and ValType | undefined | null for nullable ones. The UpdateBuilder.set() method excludes undefined from accepted values so that partial updates remain type-safe.

  ValTypeSelect logic was simplified to use this extends ... structural checks instead of TConfig extends ..., avoiding edge-cases with config-level vs runtime-resolved column traits.

  Zod schemas (createInsertSchema / createUpdateSchema) were updated to match:

  • Nullable columns → zodSchema.nullable().optional()
  • notNull columns with a default or insert function → zodSchema.optional()
  • notNull columns with no default → zodSchema (required)

  Also fixed a subtle bug in array-dimension tuple schema generation where Array(n).map(...) was replaced with Array.from({ length: n }, ...) to avoid iterating over sparse arrays.

Patch Changes

• b5382ef - Thanks to @almahdi404 !

  fix: properly handle rq nested relation order by

  Fixed orderBy clauses in nested relations (many-to-one queries) not properly resolving table aliases. The issue occurred when using orderBy within options of nested relation queries, where column references couldn't be correctly mapped to their table aliases.

  Changes include:

  • Updated Order.toQuery() and OrderSqlFn.toQuery() methods to accept optional QueryContext parameter for proper alias resolution
  • Modified nested relation subquery building to pass table alias context through orderBy operations

  Now orderBy works correctly in nested relation queries like:

  db.from(Users).relational({
    posts: {
      orderBy: [desc(Posts.createdAt)],
      limit: 5,
    },
  });