delta/python-packages/sqlalchemy.git, branch ticket_3516 github.com: zzzeek/sqlalchemy.git - Added support for "set-aggregate" functions of the form 2015-08-26T21:19:27+00:00 Mike Bayer mike_mp@zzzcomputing.com 2015-08-26T20:58:13+00:00 7c4512cbeb1cf9e4e988e833589ddc6377b5e525 ``<function> WITHIN GROUP (ORDER BY <criteria>)``, using the method :class:`.FunctionElement.within_group`. A series of common set-aggregate functions with return types derived from the set have been added. This includes functions like :class:`.percentile_cont`, :class:`.dense_rank` and others. fixes #1370 - make sure we use func.name for all _literal_as_binds in functions.py so we get consistent naming behavior for parameters. 
``<function> WITHIN GROUP (ORDER BY <criteria>)``, using the
method :class:`.FunctionElement.within_group`.  A series of common
set-aggregate functions with return types derived from the set have
been added. This includes functions like :class:`.percentile_cont`,
:class:`.dense_rank` and others.
fixes #1370
- make sure we use func.name for all _literal_as_binds in functions.py
so we get consistent naming behavior for parameters.
- Added support for the SQL-standard function :class:`.array_agg`, 2015-08-26T19:15:55+00:00 Mike Bayer mike_mp@zzzcomputing.com 2015-08-26T19:15:45+00:00 cfae9c2eaf0020be8d8acbe104cb693e0fee0796 which automatically returns an :class:`.Array` of the correct type and supports index / slice operations. As arrays are only supported on Postgresql at the moment, only actually works on Postgresql. fixes #3132 
which automatically returns an :class:`.Array` of the correct type
and supports index / slice operations.   As arrays are only
supported on Postgresql at the moment, only actually works on
Postgresql. fixes #3132
- build out a new base type for Array, as well as new any/all operators 2015-08-25T22:24:46+00:00 Mike Bayer mike_mp@zzzcomputing.com 2015-08-24T21:57:36+00:00 7024745a142e261efb6d878389d01a06673b655c - any/all work for Array as well as subqueries, accepted by MySQL - Postgresql ARRAY now subclasses Array - fixes #3516 
- any/all work for Array as well as subqueries, accepted by MySQL
- Postgresql ARRAY now subclasses Array
- fixes #3516
- Fixed two issues in the "history_meta" example where history tracking 2015-08-24T14:54:09+00:00 Mike Bayer mike_mp@zzzcomputing.com 2015-08-24T14:54:09+00:00 d57e5edbcdf915168c613cdd6da0bd7bea877fa4 could encounter empty history, and where a column keyed to an alternate attribute name would fail to track properly. Fixes courtesy Alex Fraser. 
could encounter empty history, and where a column keyed to an alternate
attribute name would fail to track properly.  Fixes courtesy
Alex Fraser.
- repair the inspection hook in sqltypes to not be fooled 2015-08-22T20:01:23+00:00 Mike Bayer mike_mp@zzzcomputing.com 2015-08-22T20:01:23+00:00 03e47a8255476d9ed50c5aec73e6c272761d67eb by mock and other __getattr__ impostors 
by mock and other __getattr__ impostors
- Added new checks for the common error case of passing mapped classes 2015-08-22T16:47:13+00:00 Mike Bayer mike_mp@zzzcomputing.com 2015-08-22T16:47:13+00:00 8712ef2f81498fe59b9636ba150833d779e60781 or mapped instances into contexts where they are interpreted as SQL bound parameters; a new exception is raised for this. fixes #3321 
or mapped instances into contexts where they are interpreted as
SQL bound parameters; a new exception is raised for this.
fixes #3321
- rework the "controlling DDL sequences" documentation to 2015-08-21T20:36:15+00:00 Mike Bayer mike_mp@zzzcomputing.com 2015-08-21T20:36:15+00:00 e0a8030048f4ad0690d3084929441bda4c21aba2 refer mostly to the DDL object; this system is primarily useful in that case, and not for built-in objects. Reference that the built-in case is not really viable right now. References #3442. 
refer mostly to the DDL object; this system is primarily useful
in that case, and not for built-in objects.  Reference that
the built-in case is not really viable right now. References #3442.
- some cleanups in compiler.py 2015-08-18T21:25:05+00:00 Mike Bayer mike_mp@zzzcomputing.com 2015-08-18T21:25:05+00:00 acda2e7d0b736e349c24905a359a4e765f829683 






- forgot to implement py3k logic for JSON.NULL
2015-08-18T20:36:56+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2015-08-18T20:34:14+00:00

871330c37907d894f021b8ec0f44b31c2460ce0c












- fix the postgresql_jsonb requirement to include the 9.4 requirement
2015-08-18T17:30:21+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2015-08-18T17:02:58+00:00

b653fedca5f0fc384c990e93d82c0780c9e76f2c

- new test for json col['x']['y']['z'] seems to fail pre PG 9.4,
fails on comparisons for non-compatible data instead of not matching
- no need to call SpecPredicate(db) directly in exclusion functions,
by using Predicate.as_predicate() the spec strings can have version
comparisons





- new test for json col['x']['y']['z'] seems to fail pre PG 9.4,
fails on comparisons for non-compatible data instead of not matching
- no need to call SpecPredicate(db) directly in exclusion functions,
by using Predicate.as_predicate() the spec strings can have version
comparisons