delta/python-packages/sqlalchemy.git/lib/sqlalchemy/orm/util.py, branch pr/1

Fixed a regression from 0.7 caused by this ticket, which

2013-05-13T20:13:15+00:00

made the check for recursion overflow in self-referential
eager joining too loose, missing a particular circumstance
where a subclass had lazy="joined" or "subquery" configured
and the load was a "with_polymorphic" against the base.
[ticket:2481]

we can always adapt to right also. suppose if right

2013-04-25T18:29:48+00:00

were an alias of a table, should add tests for that.

cleanup

2013-04-25T18:13:13+00:00

everything passes with this!!!!!!! holy crap !!!!! and its the simplest of all

2013-04-25T17:54:40+00:00

- attempt to replace the whole idea of "join_to_left" with a more

2013-04-24T22:58:09+00:00

fundamental and general purpose heuristic.   this initial approach
has about 60 tests failing but seems to have gone pretty far

- 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

- Added new helper function :func:`.was_deleted`, returns True

2013-02-20T23:24:46+00:00

if the given object was the subject of a :meth:`.Session.delete`
operation.
- An object that's deleted from a session will be de-associated with
that session fully after the transaction is committed, that is
the :func:`.object_session` function will return None.
[ticket:2658]

happy new year (see #2645)

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

- refactor of pathing mechanics, to address #2614, #2617

2012-12-02T01:12:23+00:00

- paths now store Mapper + MapperProperty now instead of string key,
so that the parent mapper for the property is known, supports same-named
properties on multiple subclasses
- the Mapper within the path is now always relevant to the property
to the right of it.  PathRegistry does the translation now, instead
of having all the outside users of PathRegistry worry about it,
to produce a path that is much more consistent.  Paths are now
consistent with mappings in all cases.  Special logic to get at
"with_polymorphic" structures and such added also.
- AliasedClass now has two modes, "use_mapper_path" and regular;
"use_mapper_path" is for all those situations where we put an AliasedClass
in for a plain class internally, and want it to "path" with the
plain mapper.
- The AliasedInsp is now the first class "entity" for an AliasedClass,
and is passed around internally and used as attr._parententity
and such.  it is the AliasedClass analogue for Mapper.

Added a new exception to detect the case where two

2012-11-24T21:14:58+00:00

subclasses are being loaded using with_polymorphic(),
each subclass contains a relationship attribute of the same
name, and eager loading is being applied to one or both.
This is an ongoing bug which can't be immediately fixed,
so since the results are usually wrong in any case it raises an
exception for now.   0.7 has the same issue, so an exception
raise here probably means the code was returning the wrong
data in 0.7.  [ticket:2614]