delta/python-packages/sqlalchemy.git/test/sql, branch rel_1_1 github.com: zzzeek/sqlalchemy.git MariaDB 10.3 updates 2018-08-30T21:13:58+00:00 Mike Bayer mike_mp@zzzcomputing.com 2018-08-30T21:12:58+00:00 1351fa138673d93c81c5c44f28711a684c9da8b5 MariaDB seems to handle some additional UPDATE/DELETE FROM syntaxes as well as some forms of INTERSECT and EXCEPT. Open up tests that expect failure for MySQL to allow success for MariaDB 10.3. Change-Id: Ia9341a82485ef7201bb8130d8dbf4a9b6976035a (cherry picked from commit 081d4275cf5c3e6842c8e0198542ff89617eaa96) 
MariaDB seems to handle some additional UPDATE/DELETE FROM
syntaxes as well as some forms of INTERSECT and EXCEPT. Open
up tests that expect failure for MySQL to allow success for
MariaDB 10.3.

Change-Id: Ia9341a82485ef7201bb8130d8dbf4a9b6976035a
(cherry picked from commit 081d4275cf5c3e6842c8e0198542ff89617eaa96)
`ValuesBase.values` inconsistency fix 2018-01-12T16:30:05+00:00 Aubrey Stark-Toller aubrey@kleetope.net 2018-01-05T20:06:23+00:00 8e112ad2cc45910a8ca860f32a3a4e138bae2e73 Fixed bug in :meth:`.Insert.values` where using the "multi-values" format in combination with :class:`.Column` objects as keys rather than strings would fail. Pull request courtesy Aubrey Stark-Toller. Change-Id: I9d3b40b5950df8f5bfdc8b1d22f9c3afb277f17f Pull-request: https://github.com/zzzeek/sqlalchemy/pull/412 Fixes: #4162 (cherry picked from commit ab2165e6d6e9b33f772e9eb3668b3e32175093c4) 
Fixed bug in :meth:`.Insert.values` where using the "multi-values"
format in combination with :class:`.Column` objects as keys rather
than strings would fail.   Pull request courtesy Aubrey Stark-Toller.

Change-Id: I9d3b40b5950df8f5bfdc8b1d22f9c3afb277f17f
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/412
Fixes: #4162
(cherry picked from commit ab2165e6d6e9b33f772e9eb3668b3e32175093c4)
Accommodate tuples for ColumnDefault.__repr__ 2017-10-31T15:40:00+00:00 Nicolas CANIART nicolas@caniart.net 2017-10-31T15:34:10+00:00 d91edf25115c12be28ee7e2cd5fe557c1dcaf8d1 Fixed bug where ``__repr__`` of :class:`.ColumnDefault` would fail if the argument were a tuple. Pull request courtesy Nicolas Caniart. Change-Id: I08aa2448ef91054c43d6068ac54cedbdf7a83d64 Pull-request: https://bitbucket.org/zzzeek/sqlalchemy/pull-requests/1 Fixes: #4126 (cherry picked from commit 5acc9b149a4f7c44b8e7fbe926c0c5de8f13b2c4) 
Fixed bug where ``__repr__`` of :class:`.ColumnDefault` would fail
if the argument were a tuple.  Pull request courtesy Nicolas Caniart.

Change-Id: I08aa2448ef91054c43d6068ac54cedbdf7a83d64
Pull-request: https://bitbucket.org/zzzeek/sqlalchemy/pull-requests/1
Fixes: #4126
(cherry picked from commit 5acc9b149a4f7c44b8e7fbe926c0c5de8f13b2c4)
Fix array_agg to accommodate ARRAY arguments 2017-10-06T15:29:51+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-10-06T15:14:29+00:00 c5785037d869f214b10880322271e8981fdf1bec Fixed bug in :func:`.array_agg` function where passing an argument that is already of type :class:`.ARRAY`, such as a Postgresql :obj:`.postgresql.array` construct, would produce a ``ValueError``, due to the function attempting to nest the arrays. Change-Id: Ibe5f6275d90e4868e6ef8a733de05acd44c05d78 Fixes: #4107 (cherry picked from commit 4bb8397ae3a9d65bd18eb1d7c951bf5121ea280a) 
Fixed bug in :func:`.array_agg` function where passing an argument
that is already of type :class:`.ARRAY`, such as a Postgresql
:obj:`.postgresql.array` construct, would produce a ``ValueError``, due
to the function attempting to nest the arrays.

Change-Id: Ibe5f6275d90e4868e6ef8a733de05acd44c05d78
Fixes: #4107
(cherry picked from commit 4bb8397ae3a9d65bd18eb1d7c951bf5121ea280a)
Support pg10 2017-10-03T17:01:58+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-10-02T15:50:05+00:00 2a8167f24159644d6a1b0d9efbf60c7b4ff93192 One test appears to use some awkward calling style with the current_date function that isn't working in pg10 anymore, this looks like an extremely old test that can be removed Also cherry-picks f846a789b78f977b4d7e8e16b412b07e77f2ab13 from master to repair 'postgres'-deprecation warning test for multiple calls within a single process Change-Id: I5f8aee0f5ed423461be5a9060c812eb0acdc7df5 (cherry picked from commit 67ee56be69687a828d3998b2f6e2caccb3fe9072) 
One test appears to use some awkward calling style
with the current_date function that isn't working in pg10
anymore, this looks like an extremely
old test that can be removed

Also cherry-picks f846a789b78f977b4d7e8e16b412b07e77f2ab13 from master
to repair 'postgres'-deprecation warning test for multiple
calls within a single process

Change-Id: I5f8aee0f5ed423461be5a9060c812eb0acdc7df5
(cherry picked from commit 67ee56be69687a828d3998b2f6e2caccb3fe9072)
Support mariadb 10.2 2017-09-29T17:21:16+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-08-19T22:39:08+00:00 917a971764d3aca120b22b39f18441562d723285 Fixed issue where CURRENT_TIMESTAMP would not reflect correctly in the MariaDB 10.2 series due to a syntax change, where the function is now represented as ``current_timestamp()``. Fixes: #4096 MariaDB 10.2 now supports CHECK constraints (warning: use version 10.2.9 or greater due to upstream issues noted in :ticket:`4097`). Reflection now takes these CHECK constraints into account when they are present in the ``SHOW CREATE TABLE`` output. Fixes: #4098 Change-Id: I8666d61814e8145ca12cbecad94019b44af868e3 (cherry picked from commit 29b752f8b24909c9c715e1b2c5e01119d1f46aa7) 
Fixed issue where CURRENT_TIMESTAMP would not reflect correctly
in the MariaDB 10.2 series due to a syntax change, where the function
is now represented as ``current_timestamp()``.

Fixes: #4096

MariaDB 10.2 now supports CHECK constraints (warning: use version 10.2.9
or greater due to upstream issues noted in :ticket:`4097`).  Reflection
now takes these CHECK constraints into account when they are present in
the ``SHOW CREATE TABLE`` output.

Fixes: #4098

Change-Id: I8666d61814e8145ca12cbecad94019b44af868e3
(cherry picked from commit 29b752f8b24909c9c715e1b2c5e01119d1f46aa7)
Support method form of any_(), all_() 2017-09-27T19:50:07+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-09-27T14:14:57+00:00 3a8a8b9bc581fd0b9b61b386e4b0c9273707aef6 Fixed bug where the recently added :meth:`.ColumnOperators.any_` and :meth:`.ColumnOperators.all_` methods didn't work when called as methods, as opposed to using the standalone functions :func:`~.expression.any_` and :func:`~.expression.all_`. Also added documentation examples for these relatively unintuitive SQL operators. Change-Id: I3e56b463e9fd146a077b9970624f50cba27f9811 Fixes: #4093 (cherry picked from commit 944c662d8add498577d6359251d4b94cd84d4011) 
Fixed bug where the recently added :meth:`.ColumnOperators.any_`
and :meth:`.ColumnOperators.all_` methods didn't work when called
as methods, as opposed to using the standalone functions
:func:`~.expression.any_` and :func:`~.expression.all_`.  Also
added documentation examples for these relatively unintuitive
SQL operators.

Change-Id: I3e56b463e9fd146a077b9970624f50cba27f9811
Fixes: #4093
(cherry picked from commit 944c662d8add498577d6359251d4b94cd84d4011)
Allow for multiple FOLLOWING/PRECEDING in a window range 2017-08-25T13:43:38+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-08-25T13:41:18+00:00 fb55270835b18e6ba942b74ee72719ce0fc4d062 Altered the range specification for window functions to allow for two of the same PRECEDING or FOLLOWING keywords in a range by allowing for the left side of the range to be positive and for the right to be negative, e.g. (1, 3) is "1 FOLLOWING AND 3 FOLLOWING". Change-Id: I7d3a6c641151bb49219104968d18dac2266f3db8 Fixes: #4053 (cherry picked from commit 3a5bbe4cbe12d180fba2b942d0467b46be705bea) 
Altered the range specification for window functions to allow
for two of the same PRECEDING or FOLLOWING keywords in a range
by allowing for the left side of the range to be positive
and for the right to be negative, e.g. (1, 3) is
"1 FOLLOWING AND 3 FOLLOWING".

Change-Id: I7d3a6c641151bb49219104968d18dac2266f3db8
Fixes: #4053
(cherry picked from commit 3a5bbe4cbe12d180fba2b942d0467b46be705bea)
- a few mysql fixes, more to come 2017-08-21T16:10:28+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-08-20T22:57:05+00:00 cc3d1e057da98adb2e33dba2894d0961273da747 Change-Id: Icdcc8ed03374251b8d3815ae58e2726ea27c14b4 (cherry picked from commit 64032a35ae3dbed0bd5bbdf4d07b3f0094684f87) 
Change-Id: Icdcc8ed03374251b8d3815ae58e2726ea27c14b4
(cherry picked from commit 64032a35ae3dbed0bd5bbdf4d07b3f0094684f87)
Add support for CACHE and ORDER to sequences 2017-07-05T20:23:13+00:00 David Moore davidm@j5int.com 2017-07-05T19:06:49+00:00 acabfc72ad79e6c049e52011b69dba65e7aae026 Added new keywords :paramref:`.Sequence.cache` and :paramref:`.Sequence.order` to :class:`.Sequence`, to allow rendering of the CACHE parameter understood by Oracle and PostgreSQL, and the ORDER parameter understood by Oracle. Pull request courtesy David Moore. Change-Id: I082c3f8ef56ef89dbaad5da9d5695be5313b0614 Pull-request: https://bitbucket.org/zzzeek/sqlalchemy/pull-requests/96 (cherry picked from commit faa6609dac2ce6e55e0f690df3ba88c13133ec5c) 
Added new keywords :paramref:`.Sequence.cache` and
:paramref:`.Sequence.order` to :class:`.Sequence`, to allow rendering
of the CACHE parameter understood by Oracle and PostgreSQL, and the
ORDER parameter understood by Oracle.  Pull request
courtesy David Moore.

Change-Id: I082c3f8ef56ef89dbaad5da9d5695be5313b0614
Pull-request: https://bitbucket.org/zzzeek/sqlalchemy/pull-requests/96
(cherry picked from commit faa6609dac2ce6e55e0f690df3ba88c13133ec5c)