delta/python-packages/sqlalchemy.git/lib/sqlalchemy/sql/compiler.py, branch pr/288 github.com: zzzeek/sqlalchemy.git Don't reorder PrimaryKeyConstraint columns if explicit 2016-06-20T16:52:31+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-06-20T15:39:01+00:00 bf03d4332ae35e2087b175f8a2e0291d2f4c9aa0 Dialed back the "order the primary key columns per auto-increment" described in :ref:`change_mysql_3216` a bit, so that if the :class:`.PrimaryKeyConstraint` is explicitly defined, the order of columns is maintained exactly, allowing control of this behavior when necessary. Change-Id: I9e7902c57a96c15968a6abf53e319acf15680da0 Fixes: #3726 
Dialed back the "order the primary key columns per auto-increment"
described in :ref:`change_mysql_3216` a bit, so that if the
:class:`.PrimaryKeyConstraint` is explicitly defined, the order
of columns is maintained exactly, allowing control of this behavior
when necessary.

Change-Id: I9e7902c57a96c15968a6abf53e319acf15680da0
Fixes: #3726
Add DDLCompiler.create_table_suffix() 2016-06-16T15:43:02+00:00 Mark Sandan msandan@utexas.edu 2016-05-24T00:08:36+00:00 d7b8b475f8a5c0ddf955157f89db3d44d0dc0d9a Allows custom dialects to add keywords after the CREATE TABLE section. Change-Id: I6fa66dfcf00ef95122f491a9115410df2746cf88 
Allows custom dialects to add keywords after the
CREATE TABLE section.

Change-Id: I6fa66dfcf00ef95122f491a9115410df2746cf88
Add TABLESAMPLE clause support. 2016-06-15T18:42:08+00:00 saarni saarni@gmail.com 2016-05-26T14:15:24+00:00 20f2f5b169d35cfee7cc21ff697e23fd00858171 The TABLESAMPLE clause allows randomly selecting an approximate percentage of rows from a table. At least DB2, Microsoft SQL Server and recent Postgresql support this standard clause. Fixes: #3718 Change-Id: I3fb8b9223e12a57100df30876b461884c58d72fa Pull-request: https://github.com/zzzeek/sqlalchemy/pull/277 
The TABLESAMPLE clause allows randomly selecting an approximate percentage
of rows from a table. At least DB2, Microsoft SQL Server and recent
Postgresql support this standard clause.

Fixes: #3718
Change-Id: I3fb8b9223e12a57100df30876b461884c58d72fa
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/277
Add ON CONFLICT support for Postgresql 2016-06-14T19:03:14+00:00 Robin Thomas robin.thomas@livestream.com 2016-04-14T16:57:15+00:00 4e9ab7a72f0ad506cf519069fd67127f63e5f2aa Fixes: #3529 Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com> Change-Id: Ie3bf6ad70d9be9f0e44938830e922db03573991a Pull-request: https://github.com/zzzeek/sqlalchemy/pull/258 
Fixes: #3529
Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com>
Change-Id: Ie3bf6ad70d9be9f0e44938830e922db03573991a
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/258
Support range specification in window function 2016-06-07T19:17:22+00:00 Phillip Cloud cpcloud@gmail.com 2016-05-02T02:26:10+00:00 d34063aa32211c9c2763fbff753601f6c20b8845 Fixes: #3049 Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com> Change-Id: Ie572095c3e25f70a1e72e1af6858e5edd89fd25e Pull-request: https://github.com/zzzeek/sqlalchemy/pull/264 
Fixes: #3049
Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com>
Change-Id: Ie572095c3e25f70a1e72e1af6858e5edd89fd25e
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/264
Add IS (NOT) DISTINCT FROM operators 2016-06-06T19:53:25+00:00 Sebastian Bank sebastian.bank@uni-leipzig.de 2016-04-12T03:16:32+00:00 3351f5f93ca1968653becbed7f1ddef7afb96077 None / True / False render as literals. For SQLite, "IS" is used as SQLite lacks "IS DISTINCT FROM" but its "IS" operator acts this way for NULL. Doctext-author: Mike Bayer <mike_mp@zzzcomputing.com> Change-Id: I9227b81f7207b42627a0349d14d40b46aa756cce Pull-request: https://github.com/zzzeek/sqlalchemy/pull/248 
None / True / False render as literals.
For SQLite, "IS" is used as SQLite lacks
"IS DISTINCT FROM" but its "IS" operator acts
this way for NULL.

Doctext-author: Mike Bayer <mike_mp@zzzcomputing.com>
Change-Id: I9227b81f7207b42627a0349d14d40b46aa756cce
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/248
- Added :meth:`.Select.lateral` and related constructs to allow 2016-03-29T21:56:02+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-03-29T21:56:02+00:00 fb9d481e898b7695de8f75402970f67776fc47e1 for the SQL standard LATERAL keyword, currently only supported by Postgresql. fixes #2857 
for the SQL standard LATERAL keyword, currently only supported
by Postgresql.  fixes #2857
- Added support for rendering "FULL OUTER JOIN" to both Core and ORM. 2016-03-28T15:50:09+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-03-28T15:50:09+00:00 d61919118072f4c31ba2ee0bd8c4ac22a92e92f4 Pull request courtesy Stefan Urbanek. fixes #1957 
Pull request courtesy Stefan Urbanek.  fixes #1957
- Fixed bug where the negation of an EXISTS expression would not 2016-03-21T14:57:40+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-03-21T14:57:40+00:00 07a4b6cbcda6e6ee6e67893c5a5d2fd01e5f125f be properly typed as boolean in the result, and also would fail to be anonymously aliased in a SELECT list as is the case with a non-negated EXISTS construct. fixes #3682 
be properly typed as boolean in the result, and also would fail to be
anonymously aliased in a SELECT list as is the case with a
non-negated EXISTS construct.
fixes #3682
- additional adjustment to the fix made in 8ad968f33100baeb3b13c7e0b724b6b79ab4277f 2016-02-22T03:49:29+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-02-22T03:46:31+00:00 eff7b4f29d2a98ef4ccd95b693c7d653eaa543eb for ref #3657. The Oracle dialect makes more use of the "select_wraps_for" feature than SQL server because Oracle doesn't have "TOP" for a limit-only select, so tests are showing more happening here. In the case where the select() has some dupe columns, these are deduped from the .c collection so a positional match between the wrapper and original can't use .inner_columns, because these collections wont match. Using _columns_plus_names instead which is the deduped collection that determines the SELECT display, which definitely have to match up. (cherry picked from commit aa9ce3f521f254da9879ede011e520ec35b8270e) 
for ref #3657.  The Oracle dialect makes more use of the "select_wraps_for"
feature than SQL server because Oracle doesn't have "TOP" for a limit-only
select, so tests are showing more happening here.  In the case where
the select() has some dupe columns, these are deduped from the .c collection
so a positional match between the wrapper and original can't use .inner_columns,
because these collections wont match.  Using _columns_plus_names
instead which is the deduped collection that determines the SELECT display,
which definitely have to match up.

(cherry picked from commit aa9ce3f521f254da9879ede011e520ec35b8270e)