fix session cursor result tip

in 2.0, we are usually not returning CursorResult for
Session.execute().

References: #12813
Change-Id: I19049b57790b5429ce7890c86e87b93c07a3f1d2
(cherry picked from commit e2bda66b5115cc628ebce9423877586c9e817feb)

diff --git a/doc/build/tutorial/data_update.rst b/doc/build/tutorial/data_update.rst
index d21b153144d18ea603c18da8110f6f10265b59d5..4b444395ea4386a4b84bbc98888fd2047e532105 100644 (file)
--- a/doc/build/tutorial/data_update.rst
+++ b/doc/build/tutorial/data_update.rst
@@ -291,8 +291,9 @@ is available from the :attr:`_engine.CursorResult.rowcount` attribute:
     specific to the DBAPI ``cursor`` object.  An instance of this subclass is
     returned when a statement is invoked via the
     :meth:`_engine.Connection.execute` method. When using the ORM, the
-    :meth:`_orm.Session.execute` method returns an object of this type for
-    all INSERT, UPDATE, and DELETE statements.
+    :meth:`_orm.Session.execute` method will normally **not** return this type
+    of object, unless the given query uses only Core :class:`.Table` objects
+    directly.
 
 Facts about :attr:`_engine.CursorResult.rowcount`: