@@ -5,7 +5,36 @@ Changelog
5
5
6
6
.. changelog ::
7
7
:version: 1.3.3
8
- :include_notes_from: unreleased
8
+ :released: January 22, 2020
9
+
10
+ .. change ::
11
+ :tags: bug, postgresql
12
+ :tickets: 637
13
+
14
+ Fixed issue where COMMENT directives for PostgreSQL failed to correctly
15
+ include an explicit schema name, as well as correct quoting rules for
16
+ schema, table, and column names. Pull request courtesy Matthew Sills.
17
+
18
+ .. change ::
19
+ :tags: usecase, operations
20
+ :tickets: 624
21
+
22
+ Added support for rendering of "computed" elements on :class: `.Column `
23
+ objects, supported in SQLAlchemy via the new :class: `.Computed ` element
24
+ introduced in version 1.3.11. Pull request courtesy Federico Caselli.
25
+
26
+ Note that there is currently no support for ALTER COLUMN to add, remove, or
27
+ modify the "GENERATED ALWAYS AS" element from a column; at least for
28
+ PostgreSQL, it does not seem to be supported by the database. Additionally,
29
+ SQLAlchemy does not currently reliably reflect the "GENERATED ALWAYS AS"
30
+ phrase from an existing column, so there is also no autogenerate support
31
+ for addition or removal of the :class: `.Computed ` element to or from an
32
+ existing column, there is only support for adding new columns that include
33
+ the :class: `.Computed ` element. In the case that the :class: `.Computed `
34
+ element is removed from the :class: `.Column ` object in the table metadata,
35
+ PostgreSQL and Oracle currently reflect the "GENERATED ALWAYS AS"
36
+ expression as the "server default" which will produce an op that tries to
37
+ drop the element as a default.
9
38
10
39
.. changelog ::
11
40
:version: 1.3.2
0 commit comments