delta/python-packages/sqlalchemy.git/test/orm/test_attributes.py, branch pr/264 github.com: zzzeek/sqlalchemy.git - liberalize list.remove() regexp as recent Pypy versions 2015-05-24T13:49:14+00:00 Mike Bayer mike_mp@zzzcomputing.com 2015-05-24T13:49:14+00:00 1bb9c99ea9f3e36e5d4a9f1d4f21f1d0a252db4a format this message differently than cpython 
format this message differently than cpython
- Fixed more regressions caused by NEVER_SET; comparisons 2015-04-20T21:38:03+00:00 Mike Bayer mike_mp@zzzcomputing.com 2015-04-20T21:38:03+00:00 a3af638e1a95d42075e25e87474663348dcf5c14 to transient objects with attributes unset would leak NEVER_SET, and negated_contains_or_equals would do so for any transient object as the comparison used only the committed value. Repaired the NEVER_SET cases, fixes #3371, and also made negated_contains_or_equals() use state_attr_by_column() just like a non-negated comparison, fixes #3374 
to transient objects with attributes unset would leak NEVER_SET,
and negated_contains_or_equals would do so for any transient
object as the comparison used only the committed value.
Repaired the NEVER_SET cases, fixes #3371, and also made
negated_contains_or_equals() use state_attr_by_column() just
like a non-negated comparison, fixes #3374
- Mapped state internals have been reworked to allow for a 50% reduction 2015-02-18T21:08:19+00:00 Mike Bayer mike_mp@zzzcomputing.com 2015-02-18T21:08:19+00:00 3209a73b92e17dd351a50c41352791baeefcd846 in callcounts specific to the "expiration" of objects, as in the "auto expire" feature of :meth:`.Session.commit` and for :meth:`.Session.expire_all`, as well as in the "cleanup" step which occurs when object states are garbage collected. fixes #3307 
in callcounts specific to the "expiration" of objects, as in
the "auto expire" feature of :meth:`.Session.commit` and
for :meth:`.Session.expire_all`, as well as in the "cleanup" step
which occurs when object states are garbage collected.
fixes #3307
- Fixed bug that affected generally the same classes of event 2014-09-18T21:49:07+00:00 Mike Bayer mike_mp@zzzcomputing.com 2014-09-18T21:49:07+00:00 b36cdefba273b8df0bc0ddf3ad072ba6031712ab as that of :ticket:`3199`, when the ``named=True`` parameter would be used. Some events would fail to register, and others would not invoke the event arguments correctly, generally in the case of when an event was "wrapped" for adaption in some other way. The "named" mechanics have been rearranged to not interfere with the argument signature expected by internal wrapper functions. fixes #3197 
as that of :ticket:`3199`, when the ``named=True`` parameter
would be used.  Some events would fail to register, and others
would not invoke the event arguments correctly, generally in the
case of when an event was "wrapped" for adaption in some other way.
The "named" mechanics have been rearranged to not interfere with
the argument signature expected by internal wrapper functions.
fixes #3197
- Added new event handlers :meth:`.AttributeEvents.init_collection` 2014-09-08T00:28:19+00:00 Mike Bayer mike_mp@zzzcomputing.com 2014-09-08T00:28:19+00:00 390207e533854ab0c3abe6b7ebc45fae1b14eaba and :meth:`.AttributeEvents.dispose_collection`, which track when a collection is first associated with an instance and when it is replaced. These handlers supersede the :meth:`.collection.linker` annotation. The old hook remains supported through an event adapter. 
and :meth:`.AttributeEvents.dispose_collection`, which track when
a collection is first associated with an instance and when it is
replaced.  These handlers supersede the :meth:`.collection.linker`
annotation. The old hook remains supported through an event adapter.
- defaultdict benchmarks faster than a namedtuple; OK 2014-08-29T20:28:19+00:00 Mike Bayer mike_mp@zzzcomputing.com 2014-08-29T20:28:19+00:00 5686472f42468afc98d7daf61b850333aebb6a9d - inline the column-based expiration operations as well 
- inline the column-based expiration operations as well
- reverse course in #3061 so that we instead no longer set None in the attribute 2014-06-23T23:50:23+00:00 Mike Bayer mike_mp@zzzcomputing.com 2014-06-23T23:50:23+00:00 f10eb28d90cbf73f4757897f52bf26722f98372e 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 
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
- Adjustment to attribute mechanics concerning when a value is 2014-05-29T23:54:51+00:00 Mike Bayer mike_mp@zzzcomputing.com 2014-05-29T23:54:51+00:00 752f2e0fc8dec13e313a00f7c9720d24d21429ed implicitly initialized to None via first access; this action, which has always resulted in a population of the attribute, now emits an attribute event just like any other attribute set operation and generates the same kind of history as one. Additionally, many mapper internal operations will no longer implicitly generate these "None" values when various never-set attributes are checked. These are subtle behavioral fixes to attribute mechanics which provide a better solution to the problem of :ticket:`3060`, which also involves recognition of attributes explicitly set to ``None`` vs. attributes that were never set. fixes #3061 
implicitly initialized to None via first access; this action,
which has always resulted in a population of the attribute,
now emits an attribute event just like any other attribute set
operation and generates the same kind of history as one.  Additionally,
many mapper internal operations will no longer implicitly generate
these "None" values when various never-set attributes are checked.
These are subtle behavioral fixes to attribute mechanics which provide
a better solution to the problem of :ticket:`3060`, which also
involves recognition of attributes explicitly set to ``None``
vs. attributes that were never set.
fixes #3061
- Fixed a few edge cases which arise in the so-called "row switch" 2014-05-29T00:01:21+00:00 Mike Bayer mike_mp@zzzcomputing.com 2014-05-29T00:01:21+00:00 bc08ee9029258b23171bb67e191452e6c739c597 scenario, where an INSERT/DELETE can be turned into an UPDATE. In this situation, a many-to-one relationship set to None, or in some cases a scalar attribute set to None, may not be detected as a net change in value, and therefore the UPDATE would not reset what was on the previous row. This is due to some as-yet unresovled side effects of the way attribute history works in terms of implicitly assuming None isn't really a "change" for a previously un-set attribute. See also :ticket:`3061`. fixes #3060 
scenario, where an INSERT/DELETE can be turned into an UPDATE.
In this situation, a many-to-one relationship set to None, or
in some cases a scalar attribute set to None, may not be detected
as a net change in value, and therefore the UPDATE would not reset
what was on the previous row.   This is due to some as-yet
unresovled side effects of the way attribute history works in terms
of implicitly assuming None isn't really a "change" for a previously
un-set attribute.  See also :ticket:`3061`. fixes #3060
Fix many typos throughout the codebase 2014-04-26T20:13:13+00:00 Alex Gaynor alex.gaynor@gmail.com 2014-04-26T20:13:13+00:00 1caa7fafbd3c9870e1bf2b2ac623872447fc804e Found using: https://github.com/intgr/topy 
Found using: https://github.com/intgr/topy