delta/python-packages/sqlalchemy.git/lib/sqlalchemy/sql, branch ticket_4074_11 github.com: zzzeek/sqlalchemy.git 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)
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)
Repair WithinGroup.get_children() 2017-06-16T17:03:58+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-06-16T13:58:03+00:00 7a47c32bb098257402f94a3d01aee1493ddbd823 Fixed AttributeError which would occur in :class:`.WithinGroup` construct during an iteration of the structure. Change-Id: I563882d93c8c32292463a605b636aa60c77e9406 Fixes: #4012 (cherry picked from commit 3a314fcea8539133947d5ec8e42a6c86e30fdf9a) 
Fixed AttributeError which would occur in :class:`.WithinGroup`
construct during an iteration of the structure.

Change-Id: I563882d93c8c32292463a605b636aa60c77e9406
Fixes: #4012
(cherry picked from commit 3a314fcea8539133947d5ec8e42a6c86e30fdf9a)
Fix a few doc typos 2017-06-02T22:36:51+00:00 Lele Gaifax lele@metapensiero.it 2017-05-22T13:03:06+00:00 fd4c414572f503e5393daeef6d5c9e7dac7d3f26 (cherry picked from commit 4779ddd865d693f4c3521fbe200a96b88ed67186) Change-Id: Ib3caafad523fac408475a2557c30be9ff39b0a65 
(cherry picked from commit 4779ddd865d693f4c3521fbe200a96b88ed67186)

Change-Id: Ib3caafad523fac408475a2557c30be9ff39b0a65
Raise if ForeignKeyConstraint created with different numbers of 2017-05-25T20:25:09+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-05-25T14:17:11+00:00 0769b41cf291529569e6e7a313327aab75555518 local and remote columns. An :class:`.ArgumentError` is now raised if a :class:`.ForeignKeyConstraint` object is created with a mismatched number of "local" and "remote" columns, which otherwise causes the internal state of the constraint to be incorrect. Note that this also impacts the condition where a dialect's reflection process produces a mismatched set of columns for a foreign key constraint. Downstream DB2 dialect has been reported as potentially causing this scenario. Change-Id: Id51c34a6c43749bb582639f9c1dc28723482f0e5 Fixes: #3949 References: #3998 (cherry picked from commit a78718b9340e9840a470300932af178ce57c0f7d) 
local and remote columns.

An :class:`.ArgumentError` is now raised if a
:class:`.ForeignKeyConstraint` object is created with a mismatched
number of "local" and "remote" columns, which otherwise causes the
internal state of the constraint to be incorrect.   Note that this
also impacts the condition where a dialect's reflection process
produces a mismatched set of columns for a foreign key constraint.

Downstream DB2 dialect has been reported as potentially causing this
scenario.

Change-Id: Id51c34a6c43749bb582639f9c1dc28723482f0e5
Fixes: #3949
References: #3998
(cherry picked from commit a78718b9340e9840a470300932af178ce57c0f7d)
- Document the most transparent way to set JSON.NULL for 2017-05-18T21:46:18+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-05-18T21:44:10+00:00 32300ea9faf7fe0681a90bf096ae7d3c891637d8 a column default. The JSON.NULL value is special in that while it is a Python-side value, it represents "do this special behavior", and is not at all like any other Python-side value for which normally, that's exactly the type of data we want back. So in this case, encourage the user to use a SQL expression that is exact, so in the ORM context, you get back what was actually persisted in the column. There's some variants of this such as literal(JSON.NULL, JSON) but text("'null'") is simpler. Change-Id: I0339fafdc03e4b2f533d53970b2f74c774f2687b Fixes: #3923 (cherry picked from commit 4d4ea792e7ea7945de9c9b1e005ce09b2feb45b5) 
a column default.

The JSON.NULL value is special in that while it is a Python-side
value, it represents "do this special behavior", and is not at all
like any other Python-side value for which normally, that's exactly
the type of data we want back.   So in this case, encourage the user
to use a SQL expression that is exact, so in the ORM context, you get
back what was actually persisted in the column.  There's some variants
of this such as literal(JSON.NULL, JSON) but text("'null'") is simpler.

Change-Id: I0339fafdc03e4b2f533d53970b2f74c774f2687b
Fixes: #3923
(cherry picked from commit 4d4ea792e7ea7945de9c9b1e005ce09b2feb45b5)
Add links to with_only_columns to Select.column, append_column 2017-05-12T13:25:07+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-05-12T13:23:44+00:00 aa14644d1ca06beda1dac338989c60e9de585a2a Provide a brief example for these two methods indicating that typically a table-bound (or other selectable) column is appended here, then link to with_only_columns documentation which has in-depth guidelines already including that one should not append columns from the current select to itself. Change-Id: I0742405a7f3c41450d337b9c633519d9cc101dfb Fixes: #3987 (cherry picked from commit 4352e220ac04d09e120c441e79b1ac12c7ca2c45) 
Provide a brief example for these two methods
indicating that typically a table-bound (or other selectable)
column is appended here, then link to with_only_columns
documentation which has in-depth guidelines already including
that one should not append columns from the current select to itself.

Change-Id: I0742405a7f3c41450d337b9c633519d9cc101dfb
Fixes: #3987
(cherry picked from commit 4352e220ac04d09e120c441e79b1ac12c7ca2c45)
- big rewrite of the Sequence documentation: 2017-05-05T19:06:19+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-05-05T18:59:39+00:00 62313dc4e555f38e60423ae13ec947ce47ab8d67 1. Sequence should be associated with MetaData always, except in the really weird case someone is sharing a Sequence among multiple metadatas. Make this a "best practice", end the confusion of #3951, #3979 2. "optional" is not a thing people use, trim this way down 3. remove confusing language Change-Id: Iab5aec319da2582092fe2615ee50430f76441aff 
1. Sequence should be associated with MetaData always,
except in the really weird case someone is sharing a Sequence
among multiple metadatas.  Make this a "best practice", end the
confusion of #3951, #3979

2. "optional" is not a thing people use, trim this way down

3. remove confusing language

Change-Id: Iab5aec319da2582092fe2615ee50430f76441aff
- add another note re: 339e2c13b0fc8e95a47d00c0f8fc5afc4b6dff9a 2017-05-05T14:40:01+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-05-05T14:39:18+00:00 8d916e7a59cd27ed297fb28678cb344c542705e9 which clarifies that ForeignKey circumvents this logic as a "convenience". issue #3978 is updated to address trying to make this consistent. Change-Id: I089acaa89f11b7a6310c2bf32916e26eb62ab9c0 (cherry picked from commit 8f830d78ba1d68ea3e10006e10e65ddb571f45ee) 
which clarifies that ForeignKey circumvents this logic as a
"convenience".   issue #3978 is updated to address trying to make
this consistent.

Change-Id: I089acaa89f11b7a6310c2bf32916e26eb62ab9c0
(cherry picked from commit 8f830d78ba1d68ea3e10006e10e65ddb571f45ee)
- add a note to MetaData.schema indicating that the Table 2017-05-05T13:20:09+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-05-05T13:19:18+00:00 abaa6da7a04f34fcea56755a61818798ce124b1d will be cataloged in the .tables collection with its fully qualified name. Fixes #3978 Change-Id: I65fa063918efc22658e93c39a0680cb83553dec8 (cherry picked from commit 339e2c13b0fc8e95a47d00c0f8fc5afc4b6dff9a) 
will be cataloged in the .tables collection with its fully
qualified name.   Fixes #3978

Change-Id: I65fa063918efc22658e93c39a0680cb83553dec8
(cherry picked from commit 339e2c13b0fc8e95a47d00c0f8fc5afc4b6dff9a)