delta/python-packages/sqlalchemy.git/test/orm/inheritance/test_basic.py, branch pr/220 github.com: zzzeek/sqlalchemy.git - Fixed 1.0 regression where a "deferred" attribute would not populate 2015-06-29T17:49:44+00:00 Mike Bayer mike_mp@zzzcomputing.com 2015-06-29T17:47:27+00:00 4d6f4ed184b94e60d5d39eff7fae678d64e9aeaa correctly if it were loaded within the "optimized inheritance load", which is a special SELECT emitted in the case of joined table inheritance used to populate expired or unloaded attributes against a joined table without loading the base table. This is related to the fact that SQLA 1.0 no longer guesses about loading deferred columns and must be directed explicitly. fixes #3468 
correctly if it were loaded within the "optimized inheritance load",
which is a special SELECT emitted in the case of joined table
inheritance used to populate expired or unloaded attributes against
a joined table without loading the base table.  This is related to
the fact that SQLA 1.0 no longer guesses about loading deferred
columns and must be directed explicitly.
fixes #3468
- use new Or() directive to test for both SQL variants here, which can vary 2014-06-22T00:27:19+00:00 Mike Bayer mike_mp@zzzcomputing.com 2014-06-22T00:27:19+00:00 20e64ad6b8bd08b966196388d0f353c53827bdbb based on hash ordering of the ClassManager 
based on hash ordering of the ClassManager
- Additional checks have been added for the case where an inheriting 2014-06-20T22:47:28+00:00 Mike Bayer mike_mp@zzzcomputing.com 2014-06-20T22:47:28+00:00 a1bbf3a005677c1371b02c54343f5407747e336d mapper is implicitly combining one of its column-based attributes with that of the parent, where those columns normally don't necessarily share the same value. This is an extension of an existing check that was added via :ticket:`1892`; however this new check emits only a warning, instead of an exception, to allow for applications that may be relying upon the existing behavior. fixes #3042 
mapper is implicitly combining one of its column-based attributes
with that of the parent, where those columns normally don't necessarily
share the same value.  This is an extension of an existing check that
was added via :ticket:`1892`; however this new check emits only a
warning, instead of an exception, to allow for applications that may
be relying upon the existing behavior.
fixes #3042
Fix many typos throughout the codebase 2014-04-26T20:13:13+00:00 Alex Gaynor alex.gaynor@gmail.com 2014-04-26T20:13:13+00:00 1caa7fafbd3c9870e1bf2b2ac623872447fc804e Found using: https://github.com/intgr/topy 
Found using: https://github.com/intgr/topy
- remove informix dialect, moved out to https://bitbucket.org/zzzeek/sqlalchemy_informixdb 2013-11-17T18:45:23+00:00 Mike Bayer mike_mp@zzzcomputing.com 2013-11-17T18:45:23+00:00 59ca4633acd42d90dc01aef9a40373ee98080481 - remove informix, maxdb, access symbols from tests etc. 
- remove informix, maxdb, access symbols from tests etc.
- additional fix for [ticket:2750] where on an update, we make sure the 2013-06-30T19:58:50+00:00 Mike Bayer mike_mp@zzzcomputing.com 2013-06-30T19:58:50+00:00 715d6cf3d10a71acd7726b7e00c3ff40b4559bc7 value is present 
value is present
add better tests for [ticket:2750] 2013-06-30T15:21:43+00:00 Mike Bayer mike_mp@zzzcomputing.com 2013-06-30T15:21:19+00:00 6ece305692399db8266fb028a9fe5f8a1af0295b 






A warning is emitted when trying to flush an object of an inherited
2013-06-30T15:09:37+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2013-06-30T15:09:37+00:00

3b24ccaf28fd85a6e54aa813fde8b3677253f67f

mapped class where the polymorphic discriminator has been assigned
to a value that is invalid for the class.   [ticket:2750]





mapped class where the polymorphic discriminator has been assigned
to a value that is invalid for the class.   [ticket:2750]







The resolution of :class:`.ForeignKey` objects to their
2013-06-23T19:58:07+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2013-06-23T18:03:47+00:00

e288aff8eae6d08b040ad9026449ff4578104d1b

target :class:`.Column` has been reworked to be as
immediate as possible, based on the moment that the
target :class:`.Column` is associated with the same
:class:`.MetaData` as this :class:`.ForeignKey`, rather
than waiting for the first time a join is constructed,
or similar. This along with other improvements allows
earlier detection of some foreign key configuration
issues.  Also included here is a rework of the
type-propagation system, so that
it should be reliable now to set the type as ``None``
on any :class:`.Column` that refers to another via
:class:`.ForeignKey` - the type will be copied from the
target column as soon as that other column is associated,
and now works for composite foreign keys as well.
[ticket:1765]





target :class:`.Column` has been reworked to be as
immediate as possible, based on the moment that the
target :class:`.Column` is associated with the same
:class:`.MetaData` as this :class:`.ForeignKey`, rather
than waiting for the first time a join is constructed,
or similar. This along with other improvements allows
earlier detection of some foreign key configuration
issues.  Also included here is a rework of the
type-propagation system, so that
it should be reliable now to set the type as ``None``
on any :class:`.Column` that refers to another via
:class:`.ForeignKey` - the type will be copied from the
target column as soon as that other column is associated,
and now works for composite foreign keys as well.
[ticket:1765]







- 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