delta/python-packages/sqlalchemy.git/test/engine, branch pr/321

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

Additions to support HAAlchemy plugin

2016-09-16T20:20:18+00:00

- add a connect=True key to connection record to support
  pre-loading of _ConnectionRecord objects
- ensure _ConnectionRecord.close() leaves the record in a good
  state for reopening
- add _ConnectionRecord.record_info for persistent storage
- add "in_use" accessor based on fairy_ref being present or not
- allow for the exclusions system and SuiteRequirements to be
  usable without the full plugin_base setup.
- move some Python-env requirements to the importable
  requirements.py module.
- allow starttime to be queried
- add additional events for engine plugins
- have "dialect" be a first-class parameter to the pool,
  ensure the engine strategy supplies it up front

Change-Id: Ibf549f7a1766e49d335cd6f5e26bacfaef9a8229

- latest mysql 5.7 also crashing on XA recovery, disable

2016-09-16T16:57:59+00:00

XA recovery for all MySQL

Change-Id: I4f77de521cd80c09fdf97e5bbe5dfd1c830dc3cb

Check for supports_execution at ClauseElement base

2016-08-31T21:04:35+00:00

Raise a more descriptive exception / message when ClauseElement
or non-SQLAlchemy objects that are not "executable" are erroneously
passed to ``.execute()``; a new exception ObjectNotExecutableError
is raised consistently in all cases.

Change-Id: I2dd393121e2c7e5b6b9e40286a2f25670876e8e4
Fixes: #3786

- a variety of test adjustments to accomodate for MySQL 5.7

2016-07-24T20:36:27+00:00

Change-Id: Ied4245433d0d7b469dae6e7394c4931d8405f387

Make boolean processors consistent between Py/C; coerce to 1/0

2016-06-23T23:58:43+00:00

The processing performed by the :class:`.Boolean` datatype for backends
that only feature integer types has been made consistent between the
pure Python and C-extension versions, in that the C-extension version
will accept any integer value from the database as a boolean, not just
zero and one; additionally, non-boolean integer values being sent to
the database are coerced to exactly zero or one, instead of being
passed as the original integer value.

Change-Id: I01e647547fd7047bd549dd70e1fa202c51e8328b
Fixes: #3730

- dont use id() to test identity as these can be recycled

2016-06-15T22:15:46+00:00

Change-Id: Ie4cb4924909d55c5962f66e36cd5325e8e8f0538

- flake8

2016-06-15T22:10:46+00:00

Change-Id: I74e369d1d71c98cb0af58dde80b7d535d17cbdf7

Deprecate FromClause.count()

2016-06-14T15:48:04+00:00

count() here is misleading in that it not only
counts from an arbitrary column in the table, it also
does not make accommodations for DISTINCT, JOIN, etc.
as the ORM-level function does.  Core should not be
attempting to provide a function like this.

Change-Id: I9916fc51ef744389a92c54660ab08e9695b8afc2
Fixes: #3724