delta/python-packages/sqlalchemy.git/lib/sqlalchemy/orm/properties.py, branch pr/18 github.com: zzzeek/sqlalchemy.git - rework PropComparator.adapted() to be PropComparator.adapt_to_entity(), 2013-06-17T23:42:43+00:00 Mike Bayer mike_mp@zzzcomputing.com 2013-06-17T22:48:17+00:00 7f82168cb6b0f0e22d387ffeca1ae82f526c2f29 passes in AliasedInsp and allows more flexibility. - rework the AliasedClass/AliasedInsp relationship so that AliasedInsp has all state and functionality. AliasedClass is just a facade. [ticket:2756] 
passes in AliasedInsp and allows more flexibility.
- rework the AliasedClass/AliasedInsp relationship so that AliasedInsp has
all state and functionality.  AliasedClass is just a facade.
[ticket:2756]
- the raw 2to3 run 2013-04-27T23:53:57+00:00 Mike Bayer mike_mp@zzzcomputing.com 2013-04-27T23:53:57+00:00 4b614b9b35cd2baddb7ca67c04bee5d70ec6a172 - went through examples/ and cleaned out excess list() calls 
- went through examples/ and cleaned out excess list() calls
A meaningful :attr:`.QueryableAttribute.info` attribute is 2013-03-09T18:24:54+00:00 Mike Bayer mike_mp@zzzcomputing.com 2013-03-09T18:24:54+00:00 852e9954aaec7205e7ebaf3d0b232e1e8ff20e63 added, which proxies down to the ``.info`` attribute on either the :class:`.schema.Column` object if directly present, or the :class:`.MapperProperty` otherwise. The full behavior is documented and ensured by tests to remain stable. [ticket:2675] 
added, which proxies down to the ``.info`` attribute on either
the :class:`.schema.Column` object if directly present, or
the :class:`.MapperProperty` otherwise.  The full behavior
is documented and ensured by tests to remain stable.
[ticket:2675]
fix non2.5 compat @property usage 2013-03-04T00:17:03+00:00 Mike Bayer mike_mp@zzzcomputing.com 2013-03-04T00:17:03+00:00 3f014926f440e3ee93f26fd70a7dec759d34a188 






dont need this conditional here
2013-03-03T19:02:54+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2013-03-03T19:02:54+00:00

8d9038b19cdf65702b70ff041d4357c140b6f3a7












- Improved checking for an existing backref name conflict during
2013-03-03T18:51:54+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2013-03-03T18:51:54+00:00

75a3f84e5f9c3be645be2ec8906e63b27e9847e5

mapper configuration; will now test for name conflicts on
superclasses and subclasses, in addition to the current mapper,
as these conflicts break things just as much.  This is new for
0.8, but see below for a warning that will also be triggered
in 0.7.11.
- Improved the error message emitted when a "backref loop" is detected,
that is when an attribute event triggers a bidirectional
assignment between two other attributes with no end.
This condition can occur not just when an object of the wrong
type is assigned, but also when an attribute is mis-configured
to backref into an existing backref pair.  Also in 0.7.11.
- A warning is emitted when a MapperProperty is assigned to a mapper
that replaces an existing property, if the properties in question
aren't plain column-based properties.   Replacement of relationship
properties is rarely (ever?) what is intended and usually refers to a
mapper mis-configuration.   Also in 0.7.11.
[ticket:2674]





mapper configuration; will now test for name conflicts on
superclasses and subclasses, in addition to the current mapper,
as these conflicts break things just as much.  This is new for
0.8, but see below for a warning that will also be triggered
in 0.7.11.
- Improved the error message emitted when a "backref loop" is detected,
that is when an attribute event triggers a bidirectional
assignment between two other attributes with no end.
This condition can occur not just when an object of the wrong
type is assigned, but also when an attribute is mis-configured
to backref into an existing backref pair.  Also in 0.7.11.
- A warning is emitted when a MapperProperty is assigned to a mapper
that replaces an existing property, if the properties in question
aren't plain column-based properties.   Replacement of relationship
properties is rarely (ever?) what is intended and usually refers to a
mapper mis-configuration.   Also in 0.7.11.
[ticket:2674]







Can set/change the "cascade" attribute on a :func:`.relationship`
2013-03-03T01:27:53+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2013-03-03T01:27:53+00:00

b83dd4dc2200bece2896a125be6d4f0911669d15

construct after it's been constructed already.  This is not
a pattern for normal use but we like to change the setting
for demonstration purposes in tutorials.





construct after it's been constructed already.  This is not
a pattern for normal use but we like to change the setting
for demonstration purposes in tutorials.







the consideration of a pending object as
2013-01-25T02:31:23+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2013-01-25T02:31:23+00:00

a477f8a61ec60b2fc343d87aa30ef6595c77727d

an "orphan" has been modified to more closely match the
behavior as that of persistent objects, which is that the object
is expunged from the :class:`.Session` as soon as it is
de-associated from any of its orphan-enabled parents.  Previously,
the pending object would be expunged only if de-associated
from all of its orphan-enabled parents.  The new flag ``legacy_is_orphan``
is added to :func:`.orm.mapper` which re-establishes the
legacy behavior. [ticket:2655]





an "orphan" has been modified to more closely match the
behavior as that of persistent objects, which is that the object
is expunged from the :class:`.Session` as soon as it is
de-associated from any of its orphan-enabled parents.  Previously,
the pending object would be expunged only if de-associated
from all of its orphan-enabled parents.  The new flag ``legacy_is_orphan``
is added to :func:`.orm.mapper` which re-establishes the
legacy behavior. [ticket:2655]







happy new year (see #2645)
2013-01-01T18:46:21+00:00

Diana Clarke
diana.joan.clarke@gmail.com

2013-01-01T18:46:21+00:00

5db55c999faae04ca338b0d4b034b3b99e0ca3fa












just a pep8 pass of lib/sqlalchemy/orm/
2012-11-19T22:19:24+00:00

Diana Clarke
diana.joan.clarke@gmail.com

2012-11-19T22:19:24+00:00

aba75454d064b157b546dbc379043f58c83a2b6d