delta/python-packages/sqlalchemy.git/test/ext/test_associationproxy.py, branch pr/147

- ensure all tests are named test_*

2014-07-30T16:18:33+00:00

- critically, py.test for unknown reasons SKIPS tests that have an init() method.

2014-05-02T22:43:12+00:00

No clue.  nosetests doesn't do this.  concerning that other tests might have the same issue.

- Fixed bug in association proxy where assigning an empty slice

2014-03-04T15:59:27+00:00

(e.g. ``x[:] = [...]``) would fail on Py3k.

- Fixed a regression in association proxy caused by :ticket:`2810` which

2014-02-27T18:29:59+00:00

caused a user-provided "getter" to no longer receive values of ``None``
when fetching scalar values from a target that is non-present.  The
check for None introduced by this change is now moved into the default
getter, so a user-provided getter will also again receive values of
None.
re: #2810

- catch the metadata on ScalarTest.test_scalar_proxy, this has been leaving itself

2013-10-25T21:56:53+00:00

around for a long time
- association proxy now returns None for proxied scalar that is also None, rather
than raising AttributeError. [ticket:2810]

correct for missing fail() methods which were lost when we removed unittest.TestCase

2013-08-26T16:30:33+00:00

clean up formatting and other linting issues

2013-08-26T16:29:27+00:00

also clarified the changelog regarding Cls.scalar != 'value'

2013-06-08T17:39:20+00:00

Added additional criterion to the ==, != comparators, used with

2013-06-08T17:23:15+00:00

scalar values, for comparisons to None to also take into account
the association record itself being non-present, in addition to the
existing test for the scalar endpoint on the association record
being NULL.  Previously, comparing ``Cls.scalar == None`` would return
records for which ``Cls.associated`` were present and
``Cls.associated.scalar`` is None, but not rows for which
``Cls.associated`` is non-present.  More significantly, the
inverse operation ``Cls.scalar != None`` *would* return ``Cls``
rows for which ``Cls.associated`` was non-present.

Additionally, added a special use case where you
can call ``Cls.scalar.has()`` with no arguments,
when ``Cls.scalar`` is a column-based value - this returns whether or
not ``Cls.associated`` has any rows present, regardless of whether
or not ``Cls.associated.scalar`` is NULL or not.
[ticket:2751]

- the raw 2to3 run

2013-04-27T23:53:57+00:00

- went through examples/ and cleaned out excess list() calls