From 292b9e6fe8f23491680d9cc60f328562e2b1c823 Mon Sep 17 00:00:00 2001 From: Simon Charette Date: Fri, 21 Mar 2025 21:50:54 -0400 Subject: Refs #27222 -- Adapted RETURNING handling to be usable for UPDATE queries. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Renamed existing methods and abstractions used for INSERT … RETURNING to be generic enough to be used in the context of UPDATEs as well. This also consolidates SQL compliant implementations on BaseDatabaseOperations. --- docs/releases/6.0.txt | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'docs') diff --git a/docs/releases/6.0.txt b/docs/releases/6.0.txt index 94376b9994..a9fe1873aa 100644 --- a/docs/releases/6.0.txt +++ b/docs/releases/6.0.txt @@ -402,6 +402,18 @@ backends. * :class:`~django.db.backends.base.schema.BaseDatabaseSchemaEditor` and PostgreSQL backends no longer use ``CASCADE`` when dropping a column. +* ``DatabaseOperations.return_insert_columns()`` and + ``DatabaseOperations.fetch_returned_insert_rows()`` methods are renamed to + ``returning_columns()`` and ``fetch_returned_rows()``, respectively, to + denote they can be used in the context ``UPDATE … RETURNING`` statements as + well as ``INSERT … RETURNING``. + +* The ``DatabaseOperations.fetch_returned_insert_columns()`` method is removed + and the ``fetch_returned_rows()`` method replacing + ``fetch_returned_insert_rows()`` expects both a ``cursor`` and + ``returning_params`` to be provided just like + ``fetch_returned_insert_columns()`` did. + Dropped support for MariaDB 10.5 -------------------------------- -- cgit v1.3