delta/python-packages/sqlalchemy.git, branch pr/188

Added test for modulo operator.

2015-07-16T23:28:23+00:00

Added support for reflected modulo operator.

2015-07-16T23:26:31+00:00

- add a note, references #3487

2015-07-15T17:07:32+00:00

- Fixed bug in :class:`.AbstractConcreteBase` extension where

2015-07-13T19:39:04+00:00

a column setup on the ABC base which had a different attribute
name vs. column name would not be correctly mapped on the final
base class.   The failure on 0.9 would be silent whereas on
1.0 it raised an ArgumentError, so may not have been noticed
prior to 1.0.
fixes #3480

- try to note under insert.values(), if you need

2015-07-09T00:37:04+00:00

"multiple parameter sets" there is a much more common case
which works equally well for INSERT/UPDATE/DELETE e.g.
executemany().   reference #3476

- add a warning suggesting to use the dictionary form of access

2015-07-05T15:16:26+00:00

if the name of the attribute being accessed is non-specific,
thereby avoiding collisions on names like items, values, keys.
fixes #3475

- fix the link here fixes 3473

2015-07-03T16:16:07+00:00

- increase the varchar here

2015-07-01T21:47:26+00:00

- Fixed 1.0 regression where value objects that override

2015-07-01T17:19:28+00:00

``__eq__()`` to return a non-boolean-capable object, such as
some geoalchemy types as well as numpy types, were being tested
for ``bool()`` during a unit of work update operation, where in
0.9 the return value of ``__eq__()`` was tested against "is True"
to guard against this.
fixes #3469

- Fixed 1.0 regression where a "deferred" attribute would not populate

2015-06-29T17:49:44+00:00

correctly if it were loaded within the "optimized inheritance load",
which is a special SELECT emitted in the case of joined table
inheritance used to populate expired or unloaded attributes against
a joined table without loading the base table.  This is related to
the fact that SQLA 1.0 no longer guesses about loading deferred
columns and must be directed explicitly.
fixes #3468