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
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