From: Mike Bayer Date: Mon, 4 Mar 2019 18:05:44 +0000 (-0500) Subject: - 1.3.0 X-Git-Tag: rel_1_3_0 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=740bb50c227d5a918e21329a3818081097fdb51a;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git - 1.3.0 --- diff --git a/doc/build/changelog/changelog_13.rst b/doc/build/changelog/changelog_13.rst index ebe2e4b555..a59266f9fc 100644 --- a/doc/build/changelog/changelog_13.rst +++ b/doc/build/changelog/changelog_13.rst @@ -12,10 +12,70 @@ .. changelog:: :version: 1.3.0 - :include_notes_from: unreleased_13 + :released: March 4, 2019 + + .. change:: + :tags: feature, schema + :tickets: 4517 + + Added new parameters :paramref:`.Table.resolve_fks` and + :paramref:`.MetaData.reflect.resolve_fks` which when set to False will + disable the automatic reflection of related tables encountered in + :class:`.ForeignKey` objects, which can both reduce SQL overhead for omitted + tables as well as avoid tables that can't be reflected for database-specific + reasons. Two :class:`.Table` objects present in the same :class:`.MetaData` + collection can still refer to each other even if the reflection of the two + tables occurred separately. + + + .. change:: + :tags: feature, orm + :tickets: 4316 + + The :meth:`.Query.get` method can now accept a dictionary of attribute keys + and values as a means of indicating the primary key value to load; is + particularly useful for composite primary keys. Pull request courtesy + Sanjana S. + + .. change:: + :tags: feature, orm + :tickets: 3133 + + A SQL expression can now be assigned to a primary key attribute for an ORM + flush in the same manner as ordinary attributes as described in + :ref:`flush_embedded_sql_expressions` where the expression will be evaulated + and then returned to the ORM using RETURNING, or in the case of pysqlite, + works using the cursor.lastrowid attribute.Requires either a database that + supports RETURNING (e.g. Postgresql, Oracle, SQL Server) or pysqlite. + + .. change:: + :tags: bug, sql + :tickets: 4509 + + The :class:`.Alias` class and related subclasses :class:`.CTE`, + :class:`.Lateral` and :class:`.TableSample` have been reworked so that it is + not possible for a user to construct the objects directly. These constructs + require that the standalone construction function or selectable-bound method + be used to instantiate new objects. + + + .. change:: + :tags: feature, engine + :tickets: 4500 + + Revised the formatting for :class:`.StatementError` when stringified. Each + error detail is broken up over multiple newlines instead of spaced out on a + single line. Additionally, the SQL representation now stringifies the SQL + statement rather than using ``repr()``, so that newlines are rendered as is. + Pull request courtesy Nate Clark. + + .. seealso:: + + :ref:`change_4500` .. changelog:: :version: 1.3.0b3 + :released: March 4, 2019 :released: February 8, 2019 .. change:: @@ -119,6 +179,7 @@ .. changelog:: :version: 1.3.0b2 + :released: March 4, 2019 :released: January 25, 2019 .. change:: @@ -346,6 +407,7 @@ .. changelog:: :version: 1.3.0b1 + :released: March 4, 2019 :released: November 16, 2018 .. change:: diff --git a/doc/build/changelog/unreleased_13/3133.rst b/doc/build/changelog/unreleased_13/3133.rst deleted file mode 100644 index c163e5296d..0000000000 --- a/doc/build/changelog/unreleased_13/3133.rst +++ /dev/null @@ -1,10 +0,0 @@ -.. change:: - :tags: feature, orm - :tickets: 3133 - - A SQL expression can now be assigned to a primary key attribute for an ORM - flush in the same manner as ordinary attributes as described in - :ref:`flush_embedded_sql_expressions` where the expression will be evaulated - and then returned to the ORM using RETURNING, or in the case of pysqlite, - works using the cursor.lastrowid attribute.Requires either a database that - supports RETURNING (e.g. Postgresql, Oracle, SQL Server) or pysqlite. diff --git a/doc/build/changelog/unreleased_13/4316.rst b/doc/build/changelog/unreleased_13/4316.rst deleted file mode 100644 index dfab94043e..0000000000 --- a/doc/build/changelog/unreleased_13/4316.rst +++ /dev/null @@ -1,8 +0,0 @@ -.. change:: - :tags: feature, orm - :tickets: 4316 - - The :meth:`.Query.get` method can now accept a dictionary of attribute keys - and values as a means of indicating the primary key value to load; is - particularly useful for composite primary keys. Pull request courtesy - Sanjana S. diff --git a/doc/build/changelog/unreleased_13/4500.rst b/doc/build/changelog/unreleased_13/4500.rst deleted file mode 100644 index 9aea02feef..0000000000 --- a/doc/build/changelog/unreleased_13/4500.rst +++ /dev/null @@ -1,13 +0,0 @@ -.. change:: - :tags: feature, engine - :tickets: 4500 - - Revised the formatting for :class:`.StatementError` when stringified. Each - error detail is broken up over multiple newlines instead of spaced out on a - single line. Additionally, the SQL representation now stringifies the SQL - statement rather than using ``repr()``, so that newlines are rendered as is. - Pull request courtesy Nate Clark. - - .. seealso:: - - :ref:`change_4500` diff --git a/doc/build/changelog/unreleased_13/4509.rst b/doc/build/changelog/unreleased_13/4509.rst deleted file mode 100644 index deb886b913..0000000000 --- a/doc/build/changelog/unreleased_13/4509.rst +++ /dev/null @@ -1,10 +0,0 @@ -.. change:: - :tags: bug, sql - :tickets: 4509 - - The :class:`.Alias` class and related subclasses :class:`.CTE`, - :class:`.Lateral` and :class:`.TableSample` have been reworked so that it is - not possible for a user to construct the objects directly. These constructs - require that the standalone construction function or selectable-bound method - be used to instantiate new objects. - diff --git a/doc/build/changelog/unreleased_13/4517.rst b/doc/build/changelog/unreleased_13/4517.rst deleted file mode 100644 index 308d61f07a..0000000000 --- a/doc/build/changelog/unreleased_13/4517.rst +++ /dev/null @@ -1,13 +0,0 @@ -.. change:: - :tags: feature, schema - :tickets: 4517 - - Added new parameters :paramref:`.Table.resolve_fks` and - :paramref:`.MetaData.reflect.resolve_fks` which when set to False will - disable the automatic reflection of related tables encountered in - :class:`.ForeignKey` objects, which can both reduce SQL overhead for omitted - tables as well as avoid tables that can't be reflected for database-specific - reasons. Two :class:`.Table` objects present in the same :class:`.MetaData` - collection can still refer to each other even if the reflection of the two - tables occurred separately. - diff --git a/doc/build/conf.py b/doc/build/conf.py index 01c4c2be51..38d2497bff 100644 --- a/doc/build/conf.py +++ b/doc/build/conf.py @@ -109,9 +109,9 @@ copyright = u'2007-2019, the SQLAlchemy authors and contributors' # The short X.Y version. version = "1.3" # The full version, including alpha/beta/rc tags. -release = "1.3.0b3" +release = "1.3.0" -release_date = "February 8, 2019" +release_date = "March 4, 2019" site_base = os.environ.get("RTD_SITE_BASE", "http://www.sqlalchemy.org") site_adapter_template = "docs_adapter.mako"