delta/python-packages/sqlalchemy.git, branch ticket_2677

- The :class:`.SessionEvents` suite now includes events to allow

2015-09-02T21:55:15+00:00

unambiguous tracking of all object lifecycle state transitions
in terms of the :class:`.Session` itself, e.g. pending,
transient,  persistent, detached.   The state of the object
within each event is also defined.
fixes #2677
- Added a new session lifecycle state :term:`deleted`.  This new state
represents an object that has been deleted from the :term:`persistent`
state and will move to the :term:`detached` state once the transaction
is committed.  This resolves the long-standing issue that objects
which were deleted existed in a gray area between persistent and
detached.   The :attr:`.InstanceState.persistent` accessor will
**no longer** report on a deleted object as persistent; the
:attr:`.InstanceState.deleted` accessor will instead be True for
these objects, until they become detached.
- The :paramref:`.Session.weak_identity_map` parameter is deprecated.
See the new recipe at :ref:`session_referencing_behavior` for
an event-based approach to maintaining strong identity map behavior.
references #3517

- add new documentation that applies to all modern SQLA versions,

2015-09-02T15:58:59+00:00

detailing ORM event recipes across the board.

- use consistent and descriptive language in all cases

2015-08-28T03:38:14+00:00

where we refer to the "weak_identity_map" option, and add additional
exposition in the session documentation which refers to it.
fixes #3517

- 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

- reword and update documentation on passive_updates=False; as virtually

2015-08-27T19:56:00+00:00

all DBs now support ON UPDATE CASCADE other than Oracle, there's no need
to try to reimplement more functionality here and users should be encouraged
to forego natural PKs unless their target platform supports them.
references #2666

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

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

ARRAY type, references #3132

- consolidate "constraints.py" into the more general "ext.py",

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

for all assorted PG SQL extensions

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

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

Merge branch 'ticket_3516'

2015-08-26T21:20:56+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.