delta/python-packages/sqlalchemy.git/test/sql, branch pr_github_284 github.com: zzzeek/sqlalchemy.git Ensure CTE internals are handled during clone 2016-06-10T21:24:36+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-06-10T21:24:36+00:00 7189d0bc82598c2d6dcbb55b054837416db2ee7d The CTE construct was missing a _copy_internals() method which would handle CTE-specific structures including _cte_alias, _restates during a clone operation. Change-Id: I9aeac9cd24d8f7ae6b70e52650d61f7c96cb6d7e Fixes: #3722 
The CTE construct was missing a _copy_internals() method
which would handle CTE-specific structures including _cte_alias,
_restates during a clone operation.

Change-Id: I9aeac9cd24d8f7ae6b70e52650d61f7c96cb6d7e
Fixes: #3722
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
Skip UniqueConstraint marked by unique=True in tometadata 2016-06-02T17:54:07+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-06-02T17:52:27+00:00 afb466fb8bd9c2f8709e79fd0fce422b83ff1d6b Fixes an issue where a Column would be copied with unique=True and at the same time the UniqueConstraint would also be copied, leading to duplicate UniqueConstraints in the target table, when tometadata() is used. Imitates the same logic used by index=True/Index to avoid duplicates. For some reason a fix was implemented for Index long ago but never for UniqueConstraint. Change-Id: Ie622ee912a6fb8bf0ea900a8b09d78c7ebc79fc0 Fixes: #3721 
Fixes an issue where a Column would be copied with unique=True
and at the same time the UniqueConstraint would also be copied,
leading to duplicate UniqueConstraints in the target table,
when tometadata() is used.   Imitates the same logic used
by index=True/Index to avoid duplicates.  For some reason
a fix was implemented for Index long ago but never for
UniqueConstraint.

Change-Id: Ie622ee912a6fb8bf0ea900a8b09d78c7ebc79fc0
Fixes: #3721
Support "blank" schema when MetaData.schema is set 2016-05-18T15:43:38+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-05-18T15:07:02+00:00 c124fa36d5af2c85c87c51d24e92387adffbe3d2 Previously, it was impossible to have a Table that has None for a schema name when the "schema" parameter on MetaData was set. A new symbol sqlalchemy.schema.BLANK_SCHEMA is added which indicates that the schema name should unconditionally be set to None. In particular, this value must be passed within cross-schema foreign key reflection, so that a Table which is in the "default" schema can be represented properly. Fixes: #3716 Change-Id: I3d24f99c22cded206c5379fd32a225e74edb7a8e 
Previously, it was impossible to have a Table that has
None for a schema name when the "schema" parameter on
MetaData was set.  A new symbol sqlalchemy.schema.BLANK_SCHEMA
is added which indicates that the schema name should unconditionally
be set to None.  In particular, this value must be passed within
cross-schema foreign key reflection, so that a Table which
is in the "default" schema can be represented properly.

Fixes: #3716
Change-Id: I3d24f99c22cded206c5379fd32a225e74edb7a8e
Don't double-process ResultMetaData for BufferedColumnResultProxy 2016-04-27T16:37:58+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-04-27T16:37:58+00:00 f3bc60bdd809235cbeb3f414717ac0e273269cf9 Fixed a bug in the result proxy used mainly by Oracle when binary and other LOB types are in play, such that when query / statement caching were used, the type-level result processors, notably that required by the binary type itself but also any other processor, would become lost after the first run of the statement due to it being removed from the cached result metadata. Change-Id: I751940866cffb4f48de46edc8137482eab59790c Fixes: #3699 
Fixed a bug in the result proxy used mainly by Oracle when binary and
other LOB types are in play, such that when query / statement caching
were used, the type-level result processors, notably that required by
the binary type itself but also any other processor, would become lost
after the first run of the statement due to it being removed from the
cached result metadata.

Change-Id: I751940866cffb4f48de46edc8137482eab59790c
Fixes: #3699
Fix result set handling for case insensitive dupe cols 2016-04-21T14:36:19+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-04-21T14:36:19+00:00 1f3e5d9826fe989f2212745f6b3592b2ef9b5e32 Fixed bug where when using ``case_sensitive=False`` with an :class:`.Engine`, the result set would fail to correctly accomodate for duplicate column names in the result set, causing an error when the statement is executed in 1.0, and preventing the "ambiguous column" exception from functioning in 1.1. Change-Id: If582bb9fdd057e4da3ae42f7180b17d1a1a2d98e Fixes: #3690 
Fixed bug where when using ``case_sensitive=False`` with an
:class:`.Engine`, the result set would fail to correctly accomodate
for duplicate column names in the result set, causing an error
when the statement is executed in 1.0, and preventing the
"ambiguous column" exception from functioning in 1.1.

Change-Id: If582bb9fdd057e4da3ae42f7180b17d1a1a2d98e
Fixes: #3690
- limit this to sqlite for now 2016-03-30T22:59:01+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-03-30T22:59:01+00:00 fdb65744d44ae9aa9d9d9635f830151f9454f319 






- move all resultproxy tests intio test_resultset
2016-03-30T21:36:03+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2016-03-30T21:36:03+00:00

03d35a833cff68013781640b1192d079ab7e1154












- 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