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

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

- use a mock here, do away with timing problems for good. need to do this

2016-06-02T22:40:46+00:00

for the rest of the timing tests

Change-Id: I06a815b1500222126a4dbc2a9a5da3ef7847e321

Implemented CHECK constraint reflection for SQLite and PostgreSQL

2016-06-01T16:57:36+00:00

Co-Authored-By: Mike Bayer 
Change-Id: Ie6cf2d2958d1c567324db9e08fef2d3186e97350
Pull-request: https://bitbucket.org/zzzeek/sqlalchemy/pull-requests/80

Merge remote-tracking branch 'origin/pr/270'

2016-05-24T20:29:49+00:00

Support "blank" schema when MetaData.schema is set

2016-05-18T15:43:38+00:00

Previously, it was impossible to have a Table that has
None for a schema name when the "schema" parameter on
MetaData was set.  A new symbol sqlalchemy.schema.BLANK_SCHEMA
is added which indicates that the schema name should unconditionally
be set to None.  In particular, this value must be passed within
cross-schema foreign key reflection, so that a Table which
is in the "default" schema can be represented properly.

Fixes: #3716
Change-Id: I3d24f99c22cded206c5379fd32a225e74edb7a8e