| Age | Commit message (Collapse) | Author |
|
refs #4459.
|
|
|
|
|
|
|
|
Thanks to vajrasky for the report and patch.
|
|
entities.
Thanks yann0 at hotmail.com for the report.
|
|
Thanks jaylett for the patch.
|
|
Thanks to Carl and Shai for the discussion.
|
|
This reverts commit 698dd82eee1cb83f51d4cd39546461bf76976b5e.
The patch introduced a backward incompatible change.
|
|
|
|
Thanks hvdklauw for the report and patch.
|
|
Thanks hjwp for the report.
|
|
|
|
|
|
|
|
Thanks Xelnor for the patch.
|
|
There were multiple cases where join promotion was a bit too aggressive.
This resulted in using outer joins where not necessary.
Refs #21150.
|
|
Added tests for a .annotate().select_related() join promotion failure.
This happened to work on master but was currently untested.
|
|
|
|
Thanks bartTC for the report.
|
|
Don't set a global default interpreted role function for reStructuredText.
Instead, use the `default-role` directive to change the default only within
the `parse_rst()` function.
Thanks Malcolm Tredinnick for the report.
|
|
Thanks ppetrid at yawd.eu for the suggestion.
|
|
|
|
SimpleListFilter) syntax.
Thanks gauss for the report.
|
|
Thanks Michael Manfre for the report, Raphaël Barrois for the patch and
Claude Paroz, Aymeric Augustin for the reviews.
Refs #7936.
|
|
|
|
- Fixed test that didn't close the files it opened
- Caught and handled exception when temp directory cannot be removed
|
|
exception.
Thanks Tuttle for the report.
|
|
Take in account platform path separator. Refs #19552.
|
|
os.symlink() is available starting with Windows Vista but can fail at
runtime.
|
|
|
|
Literals from source files with Django template language syntax don't
have a '.py' suffix anymore.
Also, the '.\' prefix is preserved to respect GNU gettext behavior on
that platform.
Refs #16903.
|
|
list links.
Thanks rm_ for the suggestion.
|
|
Test models introduced for #10733 didn't contain default value for
a BooleanField(). Check command didn't like that -> check tests failed.
|
|
In queries using .defer() together with .select_related() the values
and fields arguments didn't align properly for resolve_columns().
|
|
The bug was reported pre 1.1, and somewhere along the way it has been
fixed. So, this is tests only addition.
|
|
Thanks Aymeric Augustin for the suggestion. Refs #21165.
|
|
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.
|
|
Refs #18091.
|
|
The issue was reported against 1.3.x but has been fixed since.
|
|
Improve tests to cover slicing scenarios that could be handled in unique
ways by 3rd party database backends.
|
|
ChoiceFieldRenderer was not rendering nested choices. Added recursion
to ChoiceFieldRenderer to take nested choices and render them as
<ul>'s.
|
|
The import was done from util instead of utils leading to
PendingDeprecationWarning.
|
|
|
|
list_filter.
Thanks to onlygoldi2201 for the report and to ramiro and apollo13
for the reviews.
|
|
Also fixed a py3 incompatibility.
Thanks to brutasse for the report.
|
|
|