From: Mike Bayer Date: Sun, 27 Feb 2022 19:27:54 +0000 (-0500) Subject: remove incorrect deprecation message X-Git-Tag: rel_1_4_32~13 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d96fc604f9172daef28ef5f5e5c1074de966d527;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git remove incorrect deprecation message this message likely referred to ResultProxy, no idea how it referred to CursorResult, that's a very confusing issue. ResultProxy -> CursorResult is mostly a name change as far as backwards compat is concerned so there's not much "deprecated" here. Change-Id: Ic06bdde65a120101b2f9db22483bf3be6ff3556c --- diff --git a/doc/build/core/connections.rst b/doc/build/core/connections.rst index c0efba0f5c..97191f5aaa 100644 --- a/doc/build/core/connections.rst +++ b/doc/build/core/connections.rst @@ -74,9 +74,6 @@ pooling mechanism issues a ``rollback()`` call on the DBAPI connection so that any transactional state or locks are removed, and the connection is ready for its next use. -.. deprecated:: 2.0 The :class:`_engine.CursorResult` object is replaced in SQLAlchemy - 2.0 with a newly refined object known as :class:`_future.Result`. - Our example above illustrated the execution of a textual SQL string, which should be invoked by using the :func:`_expression.text` construct to indicate that we'd like to use textual SQL. The :meth:`_engine.Connection.execute` method can of