delta/python-packages/sqlalchemy.git/lib/sqlalchemy/testing, branch pr/302

Build string/int processors for JSONIndexType, JSONPathType

2016-08-04T16:38:58+00:00

Fixed regression in JSON datatypes where the "literal processor" for
a JSON index value, that needs to take effect for example within DDL,
would not be invoked for the value.  The native String and Integer
datatypes are now called upon from within the JSONIndexType
and JSONPathType.  This is applied to the generic, Postgresql, and
MySQL JSON types.

Change-Id: Ifa5f2acfeee57a79d01d7fc85d265a37bd27c716
Fixes: #3765

- MySQL's JSON shared implementation completely w/ sqltypes.JSON;

2016-07-25T03:14:47+00:00

this must have been an oversight.   Leave mysql.JSON in place still
as we might need to add things to it.
- CAST(json, String) still confusing MySQL drivers even mysqlclient.
Since here we're checking for the raw form of the JSON and not a typical
round trip, add a force for unicode

Change-Id: I727f4526a01a0875037cf0dede45cd074da5205a

- missing test_needs_fk for this test, fixes mysql failure

2016-06-03T20:44:12+00:00

Change-Id: I2dc6961f9b692a8bb6bfb2296d159df145dec679

Ensure 'options' is always present in foreign key info

2016-06-03T19:07:14+00:00

Regarding 0e88bcc30ed49193b91f248123f526fa30007f22, "options"
needs to be present as a key in the dictionary because Alembic
uses this as a guide to know if the backend is even capable of
reporting on foreign key options.

Change-Id: I271090f75088cfeec24315a878060f9b8a265335

- limit oracle DB reaps to identifiers generated from this

2016-06-02T21:42:51+00:00

run to prevent race conditions against concurrent runs

Change-Id: I065d1cec346ea7af03792c3cc2f30766f73c2bd3

- don't raise for stray gc connection. this just happens

2016-06-02T16:46:45+00:00

sometimes and it really breaks the build once this
error occurs.

Change-Id: I577c78d623b22a6429f8b083fe08821bc467eb7a

Let logging format messages on demand, use warning instead of deprecated warn

2016-05-03T15:29:41+00:00

- ensure engine is restored even if we had a failure in cleanup

2016-03-15T22:01:23+00:00

for stray connection

- not sure why MySQL DROP DBs fail but we can't just ignore the error

2016-03-03T15:50:18+00:00

like this

- handle parameter sets that aren't correctly formed, so that

2016-02-17T21:53:01+00:00

for example an exception object made within a test suite can
still repr (error seen in Keystone)