From a7d1fd197c02a3d7101db98070926e0b096882d3 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Sun, 23 Apr 2023 13:22:02 -0400 Subject: remove theme altogether Change-Id: Iaa5d1ac26007451c09d6982c06d8ad6ed22d30bc --- lib/sqlalchemy/sql/dml.py | 12 ------------ 1 file changed, 12 deletions(-) (limited to 'lib/sqlalchemy/sql') diff --git a/lib/sqlalchemy/sql/dml.py b/lib/sqlalchemy/sql/dml.py index 2ea3b3b34..1a7b7f21d 100644 --- a/lib/sqlalchemy/sql/dml.py +++ b/lib/sqlalchemy/sql/dml.py @@ -461,18 +461,6 @@ class UpdateBase( of fetching server-side expressions and defaults, for supporting backends only. - .. deepalchemy:: - - The :meth:`.UpdateBase.return_defaults` method is used by the ORM - for its internal work in fetching newly generated primary key - and server default values, in particular to provide the underyling - implementation of the :paramref:`_orm.Mapper.eager_defaults` - ORM feature as well as to allow RETURNING support with bulk - ORM inserts. Its behavior is fairly idiosyncratic - and is not really intended for general use. End users should - stick with using :meth:`.UpdateBase.returning` in order to - add RETURNING clauses to their INSERT, UPDATE and DELETE - statements. Normally, a single row INSERT statement will automatically populate the :attr:`.CursorResult.inserted_primary_key` attribute when executed, -- cgit v1.2.1