delta/python-packages/sqlalchemy.git/test, branch rel_1_2 github.com: zzzeek/sqlalchemy.git Fix 'email_address' being typoed as 'email_addres' in two places 2020-05-28T16:38:22+00:00 Mark Amery markrobertamery@gmail.com 2020-05-28T12:37:24+00:00 9d926287db06bf553b2b5d2c4f7eb8bfc0682be0 (cherry picked from commit 8a6e64323abeb9d08de3f68c63c6401ba1a5f847) 
(cherry picked from commit 8a6e64323abeb9d08de3f68c63c6401ba1a5f847)
Fix newly found rst issue 2019-12-31T01:02:37+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-12-31T01:01:23+00:00 e722fca0c9330e0da818af4a63f7086fba1f7661 Likely due to new versions flake8-rst-docstrings or similar, repair an incorrectly formatted code example in a doc string causing all the gerrits to fail. Change-Id: Ib2b242f435005a9e075315881c30c4a599d322e7 
Likely due to new versions flake8-rst-docstrings or similar,
repair an incorrectly formatted code example in a doc string
causing all the gerrits to fail.

Change-Id: Ib2b242f435005a9e075315881c30c4a599d322e7
Document and test modification of .values in before_compile_update 2019-05-16T00:28:17+00:00 Mike Bayer mike_mp@zzzcomputing.com 2019-05-16T00:27:30+00:00 a73009265a2d4161bf3742f8f9d4236f4ed57355 Change-Id: I2a694bcf24b06806dc98651015e7c7a8b090ff65 (cherry picked from commit 89e6beaf46ebdd626e292eb20f7b6ae0c3a9ae5c) 
Change-Id: I2a694bcf24b06806dc98651015e7c7a8b090ff65
(cherry picked from commit 89e6beaf46ebdd626e292eb20f7b6ae0c3a9ae5c)
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)
Add port comparison in __eq__() and __ne__() method to URL 2019-02-28T19:35:14+00:00 Sanjana sanjana0796@gmail.com 2019-02-28T15:16:13+00:00 b69074aec160cfb4722512e7732ccf214720515e Comparing two objects of :class:`.URL` using ``__eq__()`` did not take port number into consideration, two objects differing only by port number were considered equal. Port comparison is now added in ``__eq__()`` method of :class:`.URL`, objects differing by port number are now not equal. Additionally, ``__ne__()`` was not implemented for :class:`.URL` which caused unexpected result when ``!=`` was used in Python2, since there are no implied relationships among the comparison operators in Python2. Fixes: #4406 Closes: #4515 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/4515 Pull-request-sha: 0f15b805f07e7fca1f82ca6c3aad98d50ea705b8 Change-Id: Iba7d224f1282dc3f4b884d1a746f2d46669f551e (cherry picked from commit 9268c320bf6ea35696951875df518286dd79ad54) 
Comparing two objects of :class:`.URL` using ``__eq__()`` did not take port
number into consideration, two objects differing only by port number were
considered equal. Port comparison is now added in ``__eq__()`` method of
:class:`.URL`, objects differing by port number are now not equal.
Additionally, ``__ne__()`` was not implemented for :class:`.URL` which
caused unexpected result when ``!=`` was used in Python2, since there are no
implied relationships among the comparison operators in Python2.

Fixes: #4406
Closes: #4515
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/4515
Pull-request-sha: 0f15b805f07e7fca1f82ca6c3aad98d50ea705b8

Change-Id: Iba7d224f1282dc3f4b884d1a746f2d46669f551e
(cherry picked from commit 9268c320bf6ea35696951875df518286dd79ad54)
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)







Ensure _simple_lazy_clause bind names are fixed before cloning
2019-02-20T00:47:07+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2019-02-20T00:46:17+00:00

4d2bd4a78fc372c4e08c463cd58dffd1aa891118

Fixed a regression in 1.2 due to the introduction of baked queries for
relationship lazy loaders, where a race condition is created during the
generation of the "lazy clause" which occurs within a memoized attribute. If
two threads initialize the memoized attribute concurrently, the baked query
could be generated with bind parameter keys that are then replaced with new
keys by the next run, leading to a lazy load query that specifies the
related criteria as ``None``. The fix establishes that the parameter names
are fixed before the new clause and parameter objects are generated, so that
the names are the same every time.

Fixes: #4507
Change-Id: I605b824e028c87bc20ca8c2577227cdf6a591064
(cherry picked from commit d71f34cb2a28e8dfc410bc5bec68372be6d7c333)





Fixed a regression in 1.2 due to the introduction of baked queries for
relationship lazy loaders, where a race condition is created during the
generation of the "lazy clause" which occurs within a memoized attribute. If
two threads initialize the memoized attribute concurrently, the baked query
could be generated with bind parameter keys that are then replaced with new
keys by the next run, leading to a lazy load query that specifies the
related criteria as ``None``. The fix establishes that the parameter names
are fixed before the new clause and parameter objects are generated, so that
the names are the same every time.

Fixes: #4507
Change-Id: I605b824e028c87bc20ca8c2577227cdf6a591064
(cherry picked from commit d71f34cb2a28e8dfc410bc5bec68372be6d7c333)







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)







Adding setter to should_evaluate_none property
2019-02-13T22:29:23+00:00

sanjana
sanjana0796@gmail.com

2019-02-13T15:17:46+00:00

f4a72d3720bcc084a8bb7fb48ad40e2db30b7a6d

Fixed issue where the :class:`.JSON` type had a read-only
:attr:`.JSON.should_evaluate_none` attribute, which would cause failures
when making use of the :meth:`.TypeEngine.evaluates_none` method in
conjunction with this type.  Pull request courtesy Sanjana S.

Fixes: #4485

Closes: #4496
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/4496
Pull-request-sha: 044beb23982d411be6fe640716b1b693df0f7189

Change-Id: I1f3e1d7dec9d2ceb6ccaaa8cac158a062cf02710
(cherry picked from commit 12dad561a77506fe262d791d3135babc0be50e66)





Fixed issue where the :class:`.JSON` type had a read-only
:attr:`.JSON.should_evaluate_none` attribute, which would cause failures
when making use of the :meth:`.TypeEngine.evaluates_none` method in
conjunction with this type.  Pull request courtesy Sanjana S.

Fixes: #4485

Closes: #4496
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/4496
Pull-request-sha: 044beb23982d411be6fe640716b1b693df0f7189

Change-Id: I1f3e1d7dec9d2ceb6ccaaa8cac158a062cf02710
(cherry picked from commit 12dad561a77506fe262d791d3135babc0be50e66)