delta/python-packages/sqlalchemy.git/lib/sqlalchemy, branch pr/101

jsonb support for <@, ?| and ?& added.

2014-07-01T09:24:30+00:00

need to see if equality already works.

minor cleanup of the jsonb - had extraneous operators that where copied

2014-06-28T19:11:03+00:00

from hstore that don't apply.

Add tests for ? and @> operators.

add has_key & contains operators for jsonb (ported over from hstore)

2014-06-28T18:47:20+00:00

initial support for JSONB - this only allows you to define the JSONB

2014-06-24T07:23:21+00:00

datatype - this does not add any of the additional support for
querying/indexing yet.

- reverse course in #3061 so that we instead no longer set None in the attribute

2014-06-23T23:50:23+00:00

when we do a get; we return the None as always but we leave the dict blank
and the loader callable still in place.  The case for this implicit get on a pending object is not
super common and there really should be no change in state at all when this
operation proceeds.   This change is more dramatic as it reverses
a behavior SQLA has had since the first release.
fixes #3061

- Reverted the change for :ticket:`3060` - this is a unit of work

2014-06-23T22:42:54+00:00

fix that is updated more comprehensively in 1.0 via :ticket:`3061`.
The fix in :ticket:`3060` unfortunately produces a new issue whereby
an eager load of a many-to-one attribute can produce an event
that is interpreted into an attribute change.

- Additional checks have been added for the case where an inheriting

2014-06-20T22:47:28+00:00

mapper is implicitly combining one of its column-based attributes
with that of the parent, where those columns normally don't necessarily
share the same value.  This is an extension of an existing check that
was added via :ticket:`1892`; however this new check emits only a
warning, instead of an exception, to allow for applications that may
be relying upon the existing behavior.
fixes #3042

- The :paramref:`.Column.nullable` flag is implicitly set to ``False``

2014-06-20T22:03:28+00:00

when that :class:`.Column` is referred to in an explicit
:class:`.PrimaryKeyConstraint` for that table.  This behavior now
matches that of when the :class:`.Column` itself has the
:paramref:`.Column.primary_key` flag set to ``True``, which is
intended to be an exactly equivalent case.
fixes #3023

- Added a new type :class:`.postgresql.OID` to the Postgresql dialect.

2014-06-20T21:58:06+00:00

While "oid" is generally a private type within PG that is not exposed
in modern versions, there are some PG use cases such as large object
support where these types might be exposed, as well as within some
user-reported schema reflection use cases.
fixes #3002

- Fixed bug where column names added to ``mysql_length`` parameter

2014-06-18T14:56:23+00:00

on an index needed to have the same quoting for quoted names in
order to be recognized.  The fix makes the quotes optional but
also provides the old behavior for backwards compatibility with those
using the workaround.
fixes #3085