delta/python-packages/sqlalchemy.git/lib/sqlalchemy/orm/relationships.py, branch pr/54

wrong method name

2013-12-16T19:35:51+00:00

load_on_pending is different from enable_relationship_loading and should

2013-12-16T01:06:27+00:00

not be superseded.  both have a potential use.

- Error message when a string arg sent to :func:`.relationship` which

2013-12-12T17:49:57+00:00

doesn't resolve to a class or mapper has been corrected to work
the same way as when a non-string arg is received, which indicates
the name of the relationship which had the configurational error.
[ticket:2888]

Fix indentation issues in docstrings

2013-11-13T01:23:05+00:00

An overhaul of expression handling for special symbols particularly

2013-10-23T21:44:52+00:00

with conjunctions, e.g.
``None`` :func:`.expression.null` :func:`.expression.true`
:func:`.expression.false`, including consistency in rendering NULL
in conjunctions, "short-circuiting" of :func:`.and_` and :func:`.or_`
expressions which contain boolean constants, and rendering of
boolean constants and expressions as compared to "1" or "0" for backends
that don't feature ``true``/``false`` constants. [ticket:2804]

these are in alphabetical order

2013-10-13T21:17:00+00:00

- Added new option to :func:`.relationship` ``distinct_target_key``.

2013-10-13T20:42:32+00:00

This enables the subquery eager loader strategy to apply a DISTINCT
to the innermost SELECT subquery, to assist in the case where
duplicate rows are generated by the innermost query which corresponds
to this relationship (there's not yet a general solution to the issue
of dupe rows within subquery eager loading, however, when joins outside
of the innermost subquery produce dupes).  When the flag
is set to ``True``, the DISTINCT is rendered unconditionally, and when
it is set to ``None``, DISTINCT is rendered if the innermost relationship
targets columns that do not comprise a full primary key.
The option defaults to False in 0.8 (e.g. off by default in all cases),
None in 0.9 (e.g. automatic by default).   Thanks to Alexander Koval
for help with this. [ticket:2836]

- merge ticket_1418 branch, [ticket:1418]

2013-10-07T00:29:08+00:00

- The system of loader options has been entirely rearchitected to build
upon a much more comprehensive base, the :class:`.Load` object.  This
base allows any common loader option like :func:`.joinedload`,
:func:`.defer`, etc. to be used in a "chained" style for the purpose
of specifying options down a path, such as ``joinedload("foo").subqueryload("bar")``.
The new system supersedes the usage of dot-separated path names,
multiple attributes within options, and the usage of ``_all()`` options.
-  Added a new load option :func:`.orm.load_only`.  This allows a series
of column names to be specified as loading "only" those attributes,
deferring the rest.

- apply an import refactoring to the ORM as well

2013-08-14T23:58:34+00:00

- rework the event system so that event modules load after their
targets, dependencies are reversed
- create an improved strategy lookup system for the ORM
- rework the ORM to have very few import cycles
- move out "importlater" to just util.dependency
- other tricks to cross-populate modules in as clear a way as possible

- improve overlapping selectables, apply to both query and relationship

2013-06-04T22:23:06+00:00

- clean up inspect() calls within query._join()
- make sure join.alias(flat) propagates
- fix almost all assertion tests