[Sqlalchemy-commits] commit/sqlalchemy: 4 new changesets
Brought to you by:
zzzeek
From: Bitbucket <com...@bi...> - 2015-08-11 17:06:33
|
4 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/669a42c604e0/ Changeset: 669a42c604e0 Branch: None User: zzzeek Date: 2015-08-11 16:48:38+00:00 Summary: - pep8 test/orm/test_mapper Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/7841611413c7/ Changeset: 7841611413c7 Branch: None User: zzzeek Date: 2015-08-11 16:48:52+00:00 Summary: - pep8 test/orm/test_mapper (cherry picked from commit 669a42c604e007623aeeb50a6f01b217badc8ceb) Affected #: 1 file https://bitbucket.org/zzzeek/sqlalchemy/commits/5198b1de3102/ Changeset: 5198b1de3102 Branch: None User: zzzeek Date: 2015-08-11 17:05:17+00:00 Summary: - Fixed 1.0 regression where the "noload" loader strategy would fail to function for a many-to-one relationship. The loader used an API to place "None" into the dictionary which no longer actually writes a value; this is a side effect of :ticket:`3061`. - remove InstanceState._initialize() totally, it's used nowhere else and no longer does what it says it does - fill in fowards-port version ids throughout the changes for 1.0.9 Affected #: 5 files https://bitbucket.org/zzzeek/sqlalchemy/commits/7f3548909e5d/ Changeset: 7f3548909e5d Branch: rel_1_0 User: zzzeek Date: 2015-08-11 17:06:10+00:00 Summary: - Fixed 1.0 regression where the "noload" loader strategy would fail to function for a many-to-one relationship. The loader used an API to place "None" into the dictionary which no longer actually writes a value; this is a side effect of :ticket:`3061`. - remove InstanceState._initialize() totally, it's used nowhere else and no longer does what it says it does - fill in fowards-port version ids throughout the changes for 1.0.9 (cherry picked from commit 5198b1de31029cc985102cd13569086a7056c2f1) Affected #: 5 files Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. |