v0.46.0

Added

• With() on generated queries as a more ergonomic method to add mods on top of generated queries (thanks @daddz)
• Added Asc()/Desc()/... helpers to sm.OrderCombined for PostgreSQL/MySQL (thanks @daddz)
• Added SQLite um.SetCols(columns...) and im.SetCols(columns...) for tuple assignment in UPDATE ... SET and ON CONFLICT DO UPDATE SET (.ToExprs(...), .ToRow(...), .ToQuery(...)). SQLite renders (cols) = (exprs...); PostgreSQL ToRow still emits ROW (...). MySQL does not support tuple assignment — use multiple SetCol calls. (thanks @atzedus)

Fixed

• Fixed generated Setter.Apply wrapping all insert values in a single ExpressionFunc, which prevented BeforeInsertHooks and query mods from modifying individual column values via q.Values.Vals[row][columnIndex]. Base and SQLite codegen templates now emit one expression per column (MySQL already did). Generated SQL is unchanged. (thanks @atzedus)
• Fixed generated query mods for combined UNION/INTERSECT/EXCEPT queries dropping or misrouting the first operand's ORDER BY/LIMIT/OFFSET into the combined-result clauses. (thanks @daddz)
• Fixed PostgreSQL um / dm standalone join mods (InnerJoin, LeftJoin, etc.) applied before um.From(...) / dm.Using(...): the join is now preserved and attached to the next FROM / USING from_item instead of being dropped. (thanks @atzedus)
• Fixed/extended PostgreSQL sm.From(...): it now accepts variadic join chains (sm.From(table, joins...)), and inline joins are merged with already attached standalone joins when replacing the primary FROM source. (thanks @atzedus)

Changed

• Moved PostgreSQL SetCols tuple-assignment builder from dialect/psql/dialect/setcols.go to shared clause/setcols.go (clause.NewSetCols, clause.SetColsOptions). Dialect wrappers configure ToRow via SetColsOptions.RowPrefix (e.g. "ROW" on PostgreSQL). (thanks @atzedus)
• EQ comparisons passed to SET / ON CONFLICT DO UPDATE SET / MERGE ... UPDATE SET / MySQL ON DUPLICATE KEY UPDATE render without the extra parentheses used in WHERE / ON (e.g. SET "users"."name" = $1 vs WHERE ("users"."name" = $1)). (thanks @atzedus)
• NameAsExpr() on dialect View / Table types (PostgreSQL, SQLite, MySQL) omits a redundant AS when the alias matches the table name (for example FROM "users" instead of FROM "users" AS "users"). An explicit alias is still emitted when a schema is set at construction (AS "schema.table"). (thanks @atzedus)
• Generated slice relationship loaders (<Parent>Slice.Load<Relationship>) now stitch loaded parents and children in O(N+M) using a map keyed by the join column, instead of the previous O(N×M) nested loop. This greatly speeds up eager-loading and then-loading relationships with many rows on both sides. The map is only used for single-column joins whose key type is comparable with ==; composite keys and types with a custom compare_expr (e.g. []byte) fall back to the original nested loop, so generated behaviour is unchanged. (thanks @sandonemaki)

New Contributors

• @sandonemaki made their first contribution in #706

Full Changelog: v0.45.0...v0.46.0