@@ -5,7 +5,39 @@ Changelog
55
66.. changelog ::
77 :version: 1.18.2
8- :include_notes_from: unreleased
8+ :released: January 28, 2026
9+
10+ .. change ::
11+ :tags: usecase, operations
12+ :tickets: 1232
13+
14+ The ``primary_key `` parameter on :class: `.Column ` is now honored when
15+ :meth: `.Operations.add_column ` is used, and will emit the "PRIMARY KEY"
16+ keyword inline within the ADD COLUMN directive. This is strictly a syntax
17+ enhancement; no attempt is made to reconcile the column's primary key
18+ status with any existing primary key constraint or particular backend
19+ limitations on adding columns to the primary key.
20+
21+ .. change ::
22+ :tags: bug, typing
23+ :tickets: 1669
24+
25+ Fixed typing issue where the :paramref: `.AlterColumnOp.server_default ` and
26+ :paramref: `.AlterColumnOp.existing_server_default ` parameters failed to
27+ accommodate common SQLAlchemy SQL constructs such as ``null() `` and
28+ ``text() ``. Pull request courtesy Sebastian Kreft.
29+
30+
31+ .. change ::
32+ :tags: usecase, operations
33+ :tickets: 1780
34+
35+ Added ``inline_references `` parameter to :meth: `.Operations.add_column `
36+ which allows rendering of ``REFERENCES `` clauses inline within the ``ADD
37+ COLUMN `` directive rather than as a separate ``ADD CONSTRAINT `` directive.
38+ This syntax is supported by PostgreSQL, Oracle, MySQL 5.7+, and MariaDB
39+ 10.5+, and can provide performance benefits on large tables by avoiding
40+ full table validation when adding a nullable foreign key column.
941
1042.. changelog ::
1143 :version: 1.18.1
0 commit comments