delta/python-packages/sqlalchemy.git/test/dialect, branch pr/309 github.com: zzzeek/sqlalchemy.git Enable include_table for ON CONFLICT whereclauses 2016-09-28T22:08:30+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-09-28T22:01:57+00:00 800a18aff2927433163afec3b7a4671eabe1c2e3 Fixed issue in new PG "on conflict" construct where columns including those of the "excluded" namespace would not be table-qualified in the WHERE clauses in the statement. Change-Id: Idfefc93e7e7b0d84805e23d5436d822d606f6a0a Fixes: #3807 
Fixed issue in new PG "on conflict" construct where columns including
those of the "excluded" namespace would not be table-qualified
in the WHERE clauses in the statement.

Change-Id: Idfefc93e7e7b0d84805e23d5436d822d606f6a0a
Fixes: #3807
Add exclude_tablespaces argument to Oracle 2016-09-20T17:57:40+00:00 David Fraser davidf@j5int.com 2016-09-14T19:10:42+00:00 319c49e64ac52ef559d7a3f630de9291bb89e1dc Allows the SYSTEM and SYSAUX tablespaces to be only conditionally omitted when doing get_table_names() and get_temp_table_names(). Change-Id: Ie6995873f05163f2ce473a6a9c2d958a30681b44 Pull-request: https://github.com/zzzeek/sqlalchemy/pull/292 
Allows the SYSTEM and SYSAUX tablespaces to be only
conditionally omitted when doing get_table_names()
and get_temp_table_names().

Change-Id: Ie6995873f05163f2ce473a6a9c2d958a30681b44
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/292
Propagate kwargs to all MySQL CAST paths 2016-08-04T16:34:55+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-08-04T16:34:55+00:00 af6f4ab938f1ef66491cf239c91ffff393275d95 Change-Id: I23a6abb26bbbe3d118887d043ce761fc4572d8d2 Fixes: #3766 
Change-Id: I23a6abb26bbbe3d118887d043ce761fc4572d8d2
Fixes: #3766
- a variety of test adjustments to accomodate for MySQL 5.7 2016-07-24T20:36:27+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-07-24T20:36:27+00:00 02190234a25bb5ed2b07d25e6adcece2f5bba763 Change-Id: Ied4245433d0d7b469dae6e7394c4931d8405f387 
Change-Id: Ied4245433d0d7b469dae6e7394c4931d8405f387
Adapt "FOR UPDATE OF" with Oracle limit/offset 2016-07-05T22:30:25+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-07-05T16:48:41+00:00 f2ee514c757fc9ec33afaddc2a7b96d08b83a164 This modifies the Oracle ROWNUM limit/offset approach to accommodate for the "OF" clause in a "FOR UPDATE" phrase. The column expressions must be added to the selected subquery if necessary and adapted on the outside. Change-Id: Ia71b5fc4df6d326e73863f8ae9f96e8f1a5acfc1 Fixes: #3741 
This modifies the Oracle ROWNUM limit/offset approach
to accommodate for the "OF" clause in a "FOR UPDATE"
phrase.  The column expressions must be added to the selected
subquery if necessary and adapted on the outside.

Change-Id: Ia71b5fc4df6d326e73863f8ae9f96e8f1a5acfc1
Fixes: #3741
Repair PG BIGSERIAL w/ TypeDecorator, Variant 2016-07-04T20:54:01+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-07-04T20:37:26+00:00 428dfeee48c1fc4ceb5712b8934e90132ee57e33 Some of the dialect impl memoization for TypeDecorator necessarily keeps the top-level TypeDecorator type around, since a user-defined type will have bind and result set processing behavior. For both TypeDecorator and Variant, PG dialect needs to ensure it's looking at the SQLAlchemy type to check for SmallInteger / BigInteger. Fixes: 3739 Change-Id: I2d45fb997f17c6272d6bb826a77d2dba665adae7 (cherry picked from commit 421fa6b8bf9f0c3c5041579c89ec405ce0f5e0b0) 
Some of the dialect impl memoization for TypeDecorator
necessarily keeps the top-level TypeDecorator type
around, since a user-defined type will have bind and result
set processing behavior.  For both TypeDecorator and Variant,
PG dialect needs to ensure it's looking at the SQLAlchemy
type to check for SmallInteger / BigInteger.

Fixes: 3739
Change-Id: I2d45fb997f17c6272d6bb826a77d2dba665adae7
(cherry picked from commit 421fa6b8bf9f0c3c5041579c89ec405ce0f5e0b0)
Disable Enum string validation by default 2016-06-20T15:45:24+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-06-20T14:08:36+00:00 91a1022227499c8efce038c4a0a9bdcdb14a69d0 Rolled back the validation rules a bit in :class:`.Enum` to allow unknown string values to pass through, unless the flag ``validate_string=True`` is passed to the Enum; any other kind of object is still of course rejected. While the immediate use is to allow comparisons to enums with LIKE, the fact that this use exists indicates there may be more unknown-string-comparsion use cases than we expected, which hints that perhaps there are some unknown string-INSERT cases too. Change-Id: I7d1d79b374a7d47966d410998f77cd19294ab7b0 Fixes: #3725 
Rolled back the validation rules a bit in :class:`.Enum` to allow
unknown string values to pass through, unless the flag
``validate_string=True`` is passed to the Enum; any other kind of object is
still of course rejected.  While the immediate use
is to allow comparisons to enums with LIKE, the fact that this
use exists indicates there may be more unknown-string-comparsion use
cases than we expected, which hints that perhaps there are some
unknown string-INSERT cases too.

Change-Id: I7d1d79b374a7d47966d410998f77cd19294ab7b0
Fixes: #3725
Merge "Add ON CONFLICT support for Postgresql" 2016-06-14T19:23:17+00:00 mike bayer mike_mp@zzzcomputing.com 2016-06-14T19:23:17+00:00 cfb59ecc9bbd2f5040dd5bb8c82491851b186681 






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







Deprecate FromClause.count()
2016-06-14T15:48:04+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2016-06-13T19:18:13+00:00

f38f890849700ee1bf719a31275260e2da455bc3

count() here is misleading in that it not only
counts from an arbitrary column in the table, it also
does not make accommodations for DISTINCT, JOIN, etc.
as the ORM-level function does.  Core should not be
attempting to provide a function like this.

Change-Id: I9916fc51ef744389a92c54660ab08e9695b8afc2
Fixes: #3724





count() here is misleading in that it not only
counts from an arbitrary column in the table, it also
does not make accommodations for DISTINCT, JOIN, etc.
as the ORM-level function does.  Core should not be
attempting to provide a function like this.

Change-Id: I9916fc51ef744389a92c54660ab08e9695b8afc2
Fixes: #3724