From ba70a7d605c805ce9ea269873dd03f8b9aedfdd5 Mon Sep 17 00:00:00 2001 From: Gord Thompson Date: Tue, 23 Jan 2024 12:22:32 -0700 Subject: [PATCH] Update cascades.rst (#10918) MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit "delete-cascade" → "delete-orphan" (cherry picked from commit d0bcf95cb022934d101aa94411f320c4e3bfb6aa) --- doc/build/orm/cascades.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/build/orm/cascades.rst b/doc/build/orm/cascades.rst index 4c1e365ef7..20f96001e3 100644 --- a/doc/build/orm/cascades.rst +++ b/doc/build/orm/cascades.rst @@ -301,7 +301,7 @@ The feature by default works completely independently of database-configured In order to integrate more efficiently with this configuration, additional directives described at :ref:`passive_deletes` should be used. -.. warning:: Note that the ORM's "delete" and "delete-cascade" behavior applies +.. warning:: Note that the ORM's "delete" and "delete-orphan" behavior applies **only** to the use of the :meth:`_orm.Session.delete` method to mark individual ORM instances for deletion within the :term:`unit of work` process. It does **not** apply to "bulk" deletes, which would be emitted using -- 2.47.2