delta/python-packages/sqlalchemy.git/test/dialect, branch rel_1_2 github.com: zzzeek/sqlalchemy.git Commit transaction after SNAPSHOT isolation change 2019-03-09T18:07:16+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-03-08T23:36:33+00:00 117b05e2330d36109a7ba4e271ca896621b89372 A commit() is emitted after an isolation level change to SNAPSHOT, as both pyodbc and pymssql open an implicit transaction which blocks subsequent SQL from being emitted in the current transaction. Fixes: #4536 Change-Id: If3ba70f495bce2a35a873a3a72d1b30406e678c8 (cherry picked from commit cbc31716c2cef29f45506c6227c2154e3093c845) 
A commit() is emitted after an isolation level change to SNAPSHOT, as both
pyodbc and pymssql open an implicit transaction which blocks subsequent SQL
from being emitted in the current transaction.

Fixes: #4536
Change-Id: If3ba70f495bce2a35a873a3a72d1b30406e678c8
(cherry picked from commit cbc31716c2cef29f45506c6227c2154e3093c845)
Merge "Add NCHAR to Oracle dialect" into rel_1_2 2019-02-20T17:54:20+00:00 mike bayer mike_mp@zzzcomputing.com 2019-02-20T17:54:20+00:00 7e76aa9dd8e3ecfdf36e7707a3b809652539cb07 






revise timestamp correction scheme
2019-02-20T17:53:24+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2019-02-20T17:52:40+00:00

1fd70d6bd23c94d06a12525516054d708c7084ff

For very slow CI this test still fails so establish the date
as being between the range of what the operation took

Change-Id: I9204cd1915777ebc58bd598065b9015befb93345
(cherry picked from commit a3135c494e510095c938d0e7a08c4ffc0b4bb364)





For very slow CI this test still fails so establish the date
as being between the range of what the operation took

Change-Id: I9204cd1915777ebc58bd598065b9015befb93345
(cherry picked from commit a3135c494e510095c938d0e7a08c4ffc0b4bb364)







Add NCHAR to Oracle dialect
2019-02-19T17:16:47+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2019-02-19T17:13:04+00:00

420f294c46d1ab2d7c99f914e6dde0bddfa530bc

Added support for reflection of the :class:`.NCHAR` datatype to the Oracle
dialect, and added :class:`.NCHAR` to the list of types exported by the
Oracle dialect.

Fixes: #4506
Change-Id: I3a120b9ad714cbd0ebd8064519f43cf57e99d920
(cherry picked from commit 5fe9da55c72effe8f8425be339375dd904277ef2)





Added support for reflection of the :class:`.NCHAR` datatype to the Oracle
dialect, and added :class:`.NCHAR` to the list of types exported by the
Oracle dialect.

Fixes: #4506
Change-Id: I3a120b9ad714cbd0ebd8064519f43cf57e99d920
(cherry picked from commit 5fe9da55c72effe8f8425be339375dd904277ef2)







Set IDENTITY_INSERT for insert.values({column: expr})
2019-02-13T16:28:10+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2019-02-13T16:26:54+00:00

4a24277f0dd1c07c8ec194a3ad19fe6f9d998445

Fixed bug where the SQL Server "IDENTITY_INSERT" logic that allows an INSERT
to proceed with an explicit value on an IDENTITY column was not detecting
the case where :meth:`.Insert.values` were used with a dictionary that
contained a :class:`.Column` as key and a SQL expression as a value.

Fixes: #4499
Change-Id: Ia61cd6524b030b40a665db9c20771f0c5aa5fcd7
(cherry picked from commit 71d642711d26ee8e1e7e8b19d70be8be1eca22eb)





Fixed bug where the SQL Server "IDENTITY_INSERT" logic that allows an INSERT
to proceed with an explicit value on an IDENTITY column was not detecting
the case where :meth:`.Insert.values` were used with a dictionary that
contained a :class:`.Column` as key and a SQL expression as a value.

Fixes: #4499
Change-Id: Ia61cd6524b030b40a665db9c20771f0c5aa5fcd7
(cherry picked from commit 71d642711d26ee8e1e7e8b19d70be8be1eca22eb)







Add complete coverage and fix lower() for MySQL 88718 workaround
2019-02-11T14:12:37+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2019-02-11T14:07:03+00:00

db589a98b2213ec1423c98c9c152d2ba2f7efe83

Fixed a second regression caused by :ticket:`4344` (the first was
:ticket:`4361`), which works around MySQL issue 88718, where the lower
casing function used was not correct for Python 2 with OSX/Windows casing
conventions, which would then raise ``TypeError``.  Full coverage has been
added to this logic so that every codepath is exercised in a mock style for
all three casing conventions on all versions of Python. MySQL 8.0 has
meanwhile fixed issue 88718 so the workaround is only applies to a
particular span of MySQL 8.0 versions.

Fixes: #4492
Change-Id: I14e7237e0be4a9c21c58c921066304ae99ac4dc6
(cherry picked from commit 49197c7b36573d91b015019d4635071f9da1c216)





Fixed a second regression caused by :ticket:`4344` (the first was
:ticket:`4361`), which works around MySQL issue 88718, where the lower
casing function used was not correct for Python 2 with OSX/Windows casing
conventions, which would then raise ``TypeError``.  Full coverage has been
added to this logic so that every codepath is exercised in a mock style for
all three casing conventions on all versions of Python. MySQL 8.0 has
meanwhile fixed issue 88718 so the workaround is only applies to a
particular span of MySQL 8.0 versions.

Fixes: #4492
Change-Id: I14e7237e0be4a9c21c58c921066304ae99ac4dc6
(cherry picked from commit 49197c7b36573d91b015019d4635071f9da1c216)







Render parenthesis around sqlite expression defaults
2019-02-02T03:04:37+00:00

Bartlomiej Biernacki
pax0r@o2.pl

2019-01-31T14:33:01+00:00

104bb349803d176b617ad196e4c12294f4cfb035

Fixed bug in SQLite DDL where using an expression as a server side default
required that it be contained within parenthesis to be accepted by the
sqlite parser.  Pull request courtesy Bartlomiej Biernacki.

Fixes: #4474
Closes: #4475
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/4475
Pull-request-sha: 0af3238c69c2610333cf62082c12047d45c31ce0

Change-Id: I888c69bfba5a5ab8ffa420f512557ac311a36b31
(cherry picked from commit f7ce37e9dd493d4b60b3156f08ef4c98fd63904d)
(cherry picked from commit 620bfde695079eeab35467086956764616de037c)





Fixed bug in SQLite DDL where using an expression as a server side default
required that it be contained within parenthesis to be accepted by the
sqlite parser.  Pull request courtesy Bartlomiej Biernacki.

Fixes: #4474
Closes: #4475
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/4475
Pull-request-sha: 0af3238c69c2610333cf62082c12047d45c31ce0

Change-Id: I888c69bfba5a5ab8ffa420f512557ac311a36b31
(cherry picked from commit f7ce37e9dd493d4b60b3156f08ef4c98fd63904d)
(cherry picked from commit 620bfde695079eeab35467086956764616de037c)







Use pg_get_constraintdef for CHECK constraint reflection
2019-01-25T00:26:11+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2019-01-24T21:56:44+00:00

d5a6ea929609070b28e9b1ca70f1f60c7bfa40fb

Revised the query used when reflecting CHECK constraints to make use of the
``pg_get_constraintdef`` function, as the ``consrc`` column is being
deprecated in PG 12.  Thanks to John A Stevenson for the tip.

Fixes: #4463
Change-Id: Ie0ee9bdfddb0635db72b35c2e2e4b27f154162fd
(cherry picked from commit 377f12696bb1af17bb14f676a49ef21428d537d3)





Revised the query used when reflecting CHECK constraints to make use of the
``pg_get_constraintdef`` function, as the ``consrc`` column is being
deprecated in PG 12.  Thanks to John A Stevenson for the tip.

Fixes: #4463
Change-Id: Ie0ee9bdfddb0635db72b35c2e2e4b27f154162fd
(cherry picked from commit 377f12696bb1af17bb14f676a49ef21428d537d3)







Don't use cx_Oracle.NATIVE_INT in output type handlers
2019-01-19T15:38:49+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2019-01-19T02:30:21+00:00

b1ca92625dadce587946df157fac5456b7cf1592

Fixed regression in integer precision logic due to the refactor of the
cx_Oracle dialect in 1.2.  We now no longer apply the cx_Oracle.NATIVE_INT
type to result columns sending integer values (detected as positive
precision with scale ==0) which encounters integer overflow issues with
values that go beyond the 32 bit boundary.  Instead, the output variable
is left untyped so that cx_Oracle can choose the best option.

Fixes: #4457
Change-Id: I1e3114c2f37bf028fb1f521a3e9789a77e3a7491
(cherry picked from commit 5832f7172907a8151345d95061f93784ce4bb9b1)





Fixed regression in integer precision logic due to the refactor of the
cx_Oracle dialect in 1.2.  We now no longer apply the cx_Oracle.NATIVE_INT
type to result columns sending integer values (detected as positive
precision with scale ==0) which encounters integer overflow issues with
values that go beyond the 32 bit boundary.  Instead, the output variable
is left untyped so that cx_Oracle can choose the best option.

Fixes: #4457
Change-Id: I1e3114c2f37bf028fb1f521a3e9789a77e3a7491
(cherry picked from commit 5832f7172907a8151345d95061f93784ce4bb9b1)







Post black reformatting
2019-01-06T16:51:20+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2019-01-06T06:32:41+00:00

18abd47af32136b3c94a8a787905286d279181fa

Applied on top of a pure run of black -l 79 in
I7eda77fed3d8e73df84b3651fd6cfcfe858d4dc9,  this set of changes
resolves all remaining flake8 conditions for those codes
we have enabled in setup.cfg.

Included are resolutions for all remaining flake8 issues
including shadowed builtins, long lines, import order, unused
imports, duplicate imports, and docstring issues.

Change-Id: I4f72d3ba1380dd601610ff80b8fb06a2aff8b0fe





Applied on top of a pure run of black -l 79 in
I7eda77fed3d8e73df84b3651fd6cfcfe858d4dc9,  this set of changes
resolves all remaining flake8 conditions for those codes
we have enabled in setup.cfg.

Included are resolutions for all remaining flake8 issues
including shadowed builtins, long lines, import order, unused
imports, duplicate imports, and docstring issues.

Change-Id: I4f72d3ba1380dd601610ff80b8fb06a2aff8b0fe