delta/python-packages/sqlalchemy.git/test/orm/test_lazy_relations.py, branch pr/273

- fixes for the ORM side test for #3531.

2015-09-17T14:18:57+00:00

- The :func:`.type_coerce` construct is now a fully fledged Core

2015-09-16T22:46:53+00:00

expression element which is late-evaluated at compile time.  Previously,
the function was only a conversion function which would handle different
expression inputs by returning either a :class:`.Label` of a column-oriented
expression or a copy of a given :class:`.BindParameter` object,
which in particular prevented the operation from being logically
maintained when an ORM-level expression transformation would convert
a column to a bound parameter (e.g. for lazy loading).
fixes #3531

- fix for py3k

2015-05-07T13:50:37+00:00

- Fixed unexpected-use regression where in the odd case that the

2015-05-06T21:07:24+00:00

primaryjoin of a relationship involved comparison to an unhashable
type such as an HSTORE, lazy loads would fail due to a hash-oriented
check on the statement parameters, modified in 1.0 as a result of
:ticket:`3061` to use hashing and modified in :ticket:`3368`
to occur in cases more common than "load on pending".
The values are now checked for the ``__hash__`` attribute beforehand.
fixes #3416

- Fixed a critical regression caused by :ticket:`3061` where the

2015-04-17T20:06:04+00:00

NEVER_SET symbol could easily leak into a lazyload query, subsequent
to the flush of a pending object.  This would occur typically
for a many-to-one relationship that does not use a simple
"get" strategy.   The good news is that the fix improves efficiency
vs. 0.9, because we can now skip the SELECT statement entirely
when we detect NEVER_SET symbols present in the parameters; prior to
:ticket:`3061`, we couldn't discern if the None here were set or not.
fixes #3368

- Made a small adjustment to the mechanics of lazy loading,

2014-08-28T21:57:48+00:00

such that it has less chance of interfering with a joinload() in the
very rare circumstance that an object points to itself; in this
scenario, the object refers to itself while loading its attributes
which can cause a mixup between loaders.   The use case of
"object points to itself" is not fully supported, but the fix also
removes some overhead so for now is part of testing.
fixes #3145

- flake8

2014-08-28T21:42:41+00:00

- Fixed a very old behavior where the lazy load emitted for a one-to-many

2014-03-28T00:38:46+00:00

could inappropriately pull in the parent table, and also return results
inconsistent based on what's in the parent table, when the primaryjoin
includes some kind of discriminator against the parent table, such
as ``and_(parent.id == child.parent_id, parent.deleted == False)``.
While this primaryjoin doesn't make that much sense for a one-to-many,
it is slightly more common when applied to the many-to-one side, and
the one-to-many comes as a result of a backref.
Loading rows from ``child`` in this case would keep ``parent.deleted == False``
as is within the query, thereby yanking it into the FROM clause
and doing a cartesian product.  The new behavior will now substitute
the value of the local "parent.deleted" for that parameter as is
appropriate.   Though typically, a real-world app probably wants to use a
different primaryjoin for the o2m side in any case.
fixes #2948

- remove informix dialect, moved out to https://bitbucket.org/zzzeek/sqlalchemy_informixdb

2013-11-17T18:45:23+00:00

- remove informix, maxdb, access symbols from tests etc.

trying different approaches to test layout. in this one, the testing modules

2012-09-27T06:37:33+00:00

become an externally usable package but still remains within the main sqlalchemy parent package.
in this system, we use kind of an ugly hack to get the noseplugin imported outside of the
"sqlalchemy" package, while still making it available within sqlalchemy for usage by
third party libraries.