delta/python-packages/sqlalchemy.git/test, branch pr/197

- The :class:`.TypeDecorator` type extender will now work in conjunction

2015-08-27T22:04:25+00:00

with a :class:`.SchemaType` implementation, typically :class:`.Enum`
or :class:`.Boolean` with regards to ensuring that the per-table
events are propagated from the implementation type to the outer type.
These events are used
to ensure that the constraints or Postgresql types (e.g. ENUM)
are correctly created (and possibly dropped) along with the parent
table.
fixes #2919

- add a postgresql-specific form of array_agg() that injects the

2015-08-27T15:22:05+00:00

ARRAY type, references #3132

- add PG-specific aggregate_order_by(), references #3132

2015-08-27T14:32:21+00:00

- Added support for "set-aggregate" functions of the form

2015-08-26T21:19:27+00:00

`` WITHIN GROUP (ORDER BY )``, 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

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

- any/all work for Array as well as subqueries, accepted by MySQL
- Postgresql ARRAY now subclasses Array
- fixes #3516

- repair the inspection hook in sqltypes to not be fooled

2015-08-22T20:01:23+00:00

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

or mapped instances into contexts where they are interpreted as
SQL bound parameters; a new exception is raised for this.
fixes #3321

- fix the postgresql_jsonb requirement to include the 9.4 requirement

2015-08-18T17:30:21+00:00

- 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

- as the Concatenable mixin was changed to support calling down to

2015-08-18T16:40:18+00:00

"super" instead of hardcoding to "self.type" for the default return
value, the base Comparator was returning other_comparator.type.   It's
not clear what the rationale for this was, though in theory the
base Comparator should possibly even throw an exception if the two
types aren't the same (or of the same affinity?) .
- mysql.SET was broken on this because the bitwise version adds "0"
to the value to force an integer within column_expression, we are doing type_coerces here
now in any case so that there is no type ambiguity for this
operation