| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
The regression was caused by ecaba3602837d1e02fe1e961f7d3bf9086453259
and affected OR connected filters.
|
|
|
|
The `callable` builtin was added back in python 3.2
which is the minimal python3 version supported by django
at this point.
|
|
|
|
|
|
Thanks dan at dlo.me for the initial patch.
- Added __pow__ and __rpow__ to ExpressionNode
- Added oracle and mysql specific power expressions
- Added used-defined power function for sqlite
|
|
Thanks to flake8 path/to/file.py | awk -F ' ' '{ print $5 }' | sort | uniq
|
|
The typo could have consequences in exceptional cases, but I didn't
figure out a way to actually produce such a case, so not tests.
Report & patch by Michael Manfre.
|
|
contrib.auth.
The migration serializer now looks for a deconstruct method on any object.
|
|
|
|
The new handling allows us to do away with the whitelisting that was
required to support date and datetime objects.
|
|
Thanks Markus Holtermann for the report.
|
|
|
|
|
|
The method didn't change standard __deepcopy__ in any way.
|
|
|
|
|
|
|
|
|
|
Refs #6730.
|
|
select_related('foo').select_related('bar') is now equivalent to
select_related('foo', 'bar').
Also reworded docs to recommend select_related(*fields) over select_related()
|
|
|
|
|
|
Thanks Aymeric Augustin for the report and the documentation and
Tim Graham for the review.
|
|
Thanks jpic for the report and chmodas for working on a patch.
Reverts 2ea80b94. Refs #19362.
|
|
Thanks gcc for the report and vajrasky for the patch.
|
|
|
|
|
|
Thanks hjwp for the report.
|
|
Thanks Ramiro for the report.
|
|
|
|
|
|
There were multiple cases where join promotion was a bit too aggressive.
This resulted in using outer joins where not necessary.
Refs #21150.
|
|
Thanks to berkerpeksag for the report and to claudep
for the review.
|
|
|
|
|
|
|
|
In queries using .defer() together with .select_related() the values
and fields arguments didn't align properly for resolve_columns().
|
|
refs #17671
|
|
Avoid accessing query.extra and query.aggregates directly for .values()
queries. Refs #20950.
|
|
Added do_not_call_in_templates=True attribute to RelatedManagers
to prevent them from being called.
Thanks jbg@ for the report.
|
|
Squashed commit of the following:
commit 63ddb271a44df389b2c302e421fc17b7f0529755
Author: Aymeric Augustin <aymeric.augustin@m4x.org>
Date: Sun Sep 29 22:51:00 2013 +0200
Clarified interactions between atomic and exceptions.
commit 2899ec299228217c876ba3aa4024e523a41c8504
Author: Aymeric Augustin <aymeric.augustin@m4x.org>
Date: Sun Sep 22 22:45:32 2013 +0200
Fixed TransactionManagementError in tests.
Previous commit introduced an additional check to prevent running
queries in transactions that will be rolled back, which triggered a few
failures in the tests. In practice using transaction.atomic instead of
the low-level savepoint APIs was enough to fix the problems.
commit 4a639b059ea80aeb78f7f160a7d4b9f609b9c238
Author: Aymeric Augustin <aymeric.augustin@m4x.org>
Date: Tue Sep 24 22:24:17 2013 +0200
Allowed nesting constraint_checks_disabled inside atomic.
Since MySQL handles transactions loosely, this isn't a problem.
commit 2a4ab1cb6e83391ff7e25d08479e230ca564bfef
Author: Aymeric Augustin <aymeric.augustin@m4x.org>
Date: Sat Sep 21 18:43:12 2013 +0200
Prevented running queries in transactions that will be rolled back.
This avoids a counter-intuitive behavior in an edge case on databases
with non-atomic transaction semantics.
It prevents using savepoint_rollback() inside an atomic block without
calling set_rollback(False) first, which is backwards-incompatible in
tests.
Refs #21134.
commit 8e3db393853c7ac64a445b66e57f3620a3fde7b0
Author: Aymeric Augustin <aymeric.augustin@m4x.org>
Date: Sun Sep 22 22:14:17 2013 +0200
Replaced manual savepoints by atomic blocks.
This ensures the rollback flag is handled consistently in internal APIs.
|
|
Previously, if a database request spanned a related object manager, the
first manager encountered would cause a request to the router, and this
would bind all subsequent queries to the same database returned by the
router. Unfortunately, the first router query would be performed using
a read request to the router, resulting in bad routing information being
used if the subsequent query was actually a write.
This change defers the call to the router until the final query is acutally
made.
It includes a small *BACKWARDS INCOMPATIBILITY* on an edge case - see the
release notes for details.
Thanks to Paul Collins (@paulcollinsiii) for the excellent debugging
work and patch.
|
|
|
|
|
|
|