delta/python-packages/sqlalchemy.git/lib/sqlalchemy/sql/compiler.py, branch pr/307 github.com: zzzeek/sqlalchemy.git Allow stringify compiler to render unnamed column 2016-09-02T15:48:15+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-09-02T15:48:15+00:00 9a6947427af58eeb6ebf09ec6de2a1b7ec12d828 Stringify of expression with unnamed :class:`.Column` objects, as occurs in lots of situations including ORM error reporting, will now render the name in string context as "<name unknown>" rather than raising a compile error. Change-Id: I76f637c5eb4cfdb1b526964cb001565b97e296da Fixes: #3789 
Stringify of expression with unnamed :class:`.Column` objects, as
occurs in lots of situations including ORM error reporting,
will now render the name in string context as "<name unknown>"
rather than raising a compile error.

Change-Id: I76f637c5eb4cfdb1b526964cb001565b97e296da
Fixes: #3789
Check for supports_execution at ClauseElement base 2016-08-31T21:04:35+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-08-31T18:34:54+00:00 c7b9c84312b6b252e68ea704670d0ea7fc0042f0 Raise a more descriptive exception / message when ClauseElement or non-SQLAlchemy objects that are not "executable" are erroneously passed to ``.execute()``; a new exception ObjectNotExecutableError is raised consistently in all cases. Change-Id: I2dd393121e2c7e5b6b9e40286a2f25670876e8e4 Fixes: #3786 
Raise a more descriptive exception / message when ClauseElement
or non-SQLAlchemy objects that are not "executable" are erroneously
passed to ``.execute()``; a new exception ObjectNotExecutableError
is raised consistently in all cases.

Change-Id: I2dd393121e2c7e5b6b9e40286a2f25670876e8e4
Fixes: #3786
Work w/ prefetch even for selects, if present 2016-07-12T20:43:49+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-07-12T20:38:22+00:00 e486ef666f39f136c770c68db28f475d68e0173f Fixed bug in new CTE feature for update/insert/delete stated as a CTE inside of an enclosing statement (typically SELECT) whereby oninsert and onupdate values weren't called upon for the embedded statement. This is accomplished by consulting prefetch for all statements. The collection is also broken into separate insert/update collections so that we don't need to consult toplevel self.isinsert to determine if the prefetch is for an insert or an update. What we don't yet test for are CTE combinations that have both insert/update in one statement, though these should now work in theory provided the underlying database supports such a statement. Change-Id: I3b6a860e22c86743c91c56a7ec751ff706f66f64 Fixes: #3745 
Fixed bug in new CTE feature for update/insert/delete stated
as a CTE inside of an enclosing statement (typically SELECT) whereby
oninsert and onupdate values weren't called upon for the embedded
statement.

This is accomplished by consulting prefetch
for all statements.  The collection is also broken into
separate insert/update collections so that we don't need to
consult toplevel self.isinsert to determine if the prefetch
is for an insert or an update.  What we don't yet test for
are CTE combinations that have both insert/update in one
statement, though these should now work in theory provided
the underlying database supports such a statement.

Change-Id: I3b6a860e22c86743c91c56a7ec751ff706f66f64
Fixes: #3745
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