From a3eb3863dca7a80d50964c0298a356e75526cefd Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Mon, 16 Jun 2025 14:02:26 -0400 Subject: [PATCH] changelog edits Change-Id: I5bd111c1a2110bb6c386d40295836aae87922c32 --- docs/build/unreleased/1671.rst | 10 ++++++++++ docs/build/unreleased/1672.rst | 10 ---------- 2 files changed, 10 insertions(+), 10 deletions(-) create mode 100644 docs/build/unreleased/1671.rst delete mode 100644 docs/build/unreleased/1672.rst diff --git a/docs/build/unreleased/1671.rst b/docs/build/unreleased/1671.rst new file mode 100644 index 00000000..dc0d5fb1 --- /dev/null +++ b/docs/build/unreleased/1671.rst @@ -0,0 +1,10 @@ +.. change:: + :tags: bug, autogenerate + :tickets: 1671 + + Fixed issue where dialect-specific keyword arguments in ``dialect_kwargs`` + were not rendered when rendering the :meth:`.Operations.create_foreign_key` + operation. This prevented dialect-specific keywords from being rendered + using custom :class:`.Rewriter` recipes that modify + :class:`.ops.CreateForeignKeyOp`, similar to other issues such as + :ticket:`1635`. Pull request courtesy Justin Malin. diff --git a/docs/build/unreleased/1672.rst b/docs/build/unreleased/1672.rst deleted file mode 100644 index 0c636bb8..00000000 --- a/docs/build/unreleased/1672.rst +++ /dev/null @@ -1,10 +0,0 @@ -.. change:: - :tags: usecase, operations - :tickets: 1671 - Fixed an issue where dialect-specific keyword arguments, dialect_kwargs, were - not passed through when using the op.create_foreign_key() operation. This - prevented the use of backend-specific foreign key options, such as - postgresql_not_valid for PostgreSQL constraints. The renderer for - ops.CreateForeignKeyOp now correctly includes these arguments, aligning its - behavior with other constraint operations. - Pull request courtesy of Justin Malin. -- 2.47.3