delta/python-packages/sqlalchemy.git/lib/sqlalchemy/orm/mapper.py, branch pr/4

dial back the default "flatness" a bit, it will be there for joinedload and query.join(), but if

2013-06-06T22:06:02+00:00

you're dealing with aliased() or with_polymorphic() you need to say "flat=True".  Just the one
flag though, "flat" implies "aliased".

repair py3kisms in key ORM modules

2013-05-26T17:09:38+00:00

import of "sqlalchemy" and "sqlalchemy.orm" works.

2013-04-28T00:58:13+00:00

- the raw 2to3 run

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

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

Improved the behavior of instance management regarding

2013-04-20T06:45:08+00:00

the creation of strong references within the Session;
an object will no longer have an internal reference cycle
created if it's in the transient state or moves into the
detached state - the strong ref is created only when the
object is attached to a Session and is removed when the
object is detached.  This makes it somewhat safer for an
object to have a `__del__()` method, even though this is
not recommended, as relationships with backrefs produce
cycles too.  A warning has been added when a class with
a `__del__()` method is mapped.
[ticket:2708]

Fixed bug whereby ORM would run the wrong kind of

2013-04-12T00:04:57+00:00

query when refreshing an inheritance-mapped class
where the superclass was mapped to a non-Table
object, like a custom join() or a select(),
running a query that assumed a hierarchy that's
mapped to individual Table-per-class.
[ticket:2697]

- Fixed bug in unit of work whereby a joined-inheritance

2013-04-01T17:37:35+00:00

  subclass could insert the row for the "sub" table
  before the parent table, if the two tables had no
  ForeignKey constraints set up between them.
  Also in 0.7.11. [ticket:2689]
- fix a glitch in the assertsql.CompiledSQL fixture regarding
when a multiparam compiledSQL is used within an AllOf
- add a new utility function randomize_unitofwork() which
does the function of --reversetop

- remove all compat items that are pre-2.5 (hooray)

2013-03-09T22:26:16+00:00

- other cleanup
- don't need compat.decimal, that approach never panned out. hopefully
outside libs aren't pulling it in, they shouldn't be

- Improved checking for an existing backref name conflict during

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

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]

the consideration of a pending object as

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

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]