diff options
| -rw-r--r-- | doc/build/changelog/changelog_11.rst | 11 | ||||
| -rw-r--r-- | doc/build/changelog/migration_11.rst | 11 |
2 files changed, 22 insertions, 0 deletions
diff --git a/doc/build/changelog/changelog_11.rst b/doc/build/changelog/changelog_11.rst index 373fe4c3a..2a0e609b6 100644 --- a/doc/build/changelog/changelog_11.rst +++ b/doc/build/changelog/changelog_11.rst @@ -22,6 +22,17 @@ :version: 1.1.0b1 .. change:: + :tags: feature, sqlite + :tickets: 3629 + + The SQLite dialect now reflects the names of primary key constraints. + Pull request courtesy Diana Clarke. + + .. seealso:: + + :ref:`change_3629` + + .. change:: :tags: feature, sql :tickets: 2857 diff --git a/doc/build/changelog/migration_11.rst b/doc/build/changelog/migration_11.rst index 13749b047..64ed2d9e2 100644 --- a/doc/build/changelog/migration_11.rst +++ b/doc/build/changelog/migration_11.rst @@ -2086,6 +2086,17 @@ the``CREATE INDEX`` DDL didn't work correctly for a schema-bound table and the :meth:`.Inspector.get_foreign_keys` method will now indicate the given schema in the results. Cross-schema foreign keys aren't supported. +.. _change_3629: + +Reflection of the name of PRIMARY KEY constraints +-------------------------------------------------- + +The SQLite backend now takes advantage of the "sqlite_master" view +of SQLite in order to extract the name of the primary key constraint +of a table from the original DDL, in the same way that is achieved for +foreign key constraints in recent SQLAlchemy versions. + +:ticket:`3629` Dialect Improvements and Changes - SQL Server ============================================= |