delta/python-packages/sqlalchemy.git/lib/sqlalchemy/engine/result.py, branch pr_github_383

Refactor for cx_Oracle version 6

2017-09-11T18:17:10+00:00

Drops support for cx_Oracle prior to version 5.x, reworks
numeric and binary support.

Fixes: #4064

Change-Id: Ib9ae9aba430c15cd2a6eeb4e5e3fd8e97b5fe480

ResultProxy won't autoclose connection until state flag is set

2017-04-04T01:13:08+00:00

Changed the mechanics of :class:`.ResultProxy` to unconditionally
delay the "autoclose" step until the :class:`.Connection` is done
with the object; in the case where Postgresql ON CONFLICT with
RETURNING returns no rows, autoclose was occurring in this previously
non-existent use case, causing the usual autocommit behavior that
occurs unconditionally upon INSERT/UPDATE/DELETE to fail.

Change-Id: I235a25daf4381b31f523331f810ea04450349722
Fixes: #3955
(cherry picked from commit 8ee363e4917b0dcd64a83b6d26e465c9e61e0ea5)
(cherry picked from commit f52fb5282a046d26b6ee2778e03b995eb117c2ee)

update for 2017 copyright

2017-01-04T17:39:24+00:00

Change-Id: I4e8c2aa8fe817bb2af8707410fa0201f938781de

Spelling fixes

2016-10-08T17:42:50+00:00

Handle BaseException in all _handle_dbapi_error

2016-09-21T22:39:31+00:00

Tests illustrate that exceptions like GreenletExit and
even KeyboardInterrupt can corrupt the state of a DBAPI
connection like that of pymysql and mysqlclient.   Intercept
BaseException errors within the handle_error scheme and
invalidate just the connection alone in this case, but not
the whole pool.

The change is backwards-incompatible with a program that
currently intercepts ctrl-C within a database transaction
and wants to continue working on that transaction.  Ensure
the event hook can be used to reverse this behavior.

Change-Id: Ifaa013c13826d123eef34e32b7e79fff74f1b21b
Fixes: #3803

Fix typo in config result.py docs

2016-05-16T11:02:30+00:00

Don't double-process ResultMetaData for BufferedColumnResultProxy

2016-04-27T16:37:58+00:00

Fixed a bug in the result proxy used mainly by Oracle when binary and
other LOB types are in play, such that when query / statement caching
were used, the type-level result processors, notably that required by
the binary type itself but also any other processor, would become lost
after the first run of the statement due to it being removed from the
cached result metadata.

Change-Id: I751940866cffb4f48de46edc8137482eab59790c
Fixes: #3699

Fix result set handling for case insensitive dupe cols

2016-04-21T14:36:19+00:00

Fixed bug where when using ``case_sensitive=False`` with an
:class:`.Engine`, the result set would fail to correctly accomodate
for duplicate column names in the result set, causing an error
when the statement is executed in 1.0, and preventing the
"ambiguous column" exception from functioning in 1.1.

Change-Id: If582bb9fdd057e4da3ae42f7180b17d1a1a2d98e
Fixes: #3690

- make sure negative row indexes are based on the size of the

2016-03-30T21:27:53+00:00

number of columns we're actually reporting on
- add more tests for negative row index
- changelog/migration

Merge remote-tracking branch 'origin/pr/231' into pr231

2016-03-30T21:05:30+00:00