| Age | Commit message (Collapse) | Author |
|
|
|
Also unit-tested django.utils.log.RequireDebugTrue for consistency.
|
|
An index on TextField results in a warning message when running tests
on MySQL or SQLite, and the test using the TextField was PostgreSQL
only in any case.
|
|
|
|
Thanks qcwxezdas for the report. Refs #13839.
|
|
Refs #9893, #18515.
Thanks Russell for the report.
|
|
To make sure changes in 35d1cd0 don't break anything. Refs #19505.
|
|
The test introduced in 4b278131 accidentally passed because of a
limitation of Python < 3.3.
Refs #17758, #7581.
|
|
redirect urls.
Work by Julien Phalip.
Refs #8001, #18310, #19505. See also 0b908b92a2ca4fb74a103e96bb75c53c05d0a428.
|
|
Refs #17758.
|
|
|
|
|
|
|
|
|
|
|
|
Thanks aliva for the report and claudep for the feedback.
|
|
The added promotion logic is based on promoting any joins used in only
some of the childs of an OR clause unless the join existed before the
OR clause addition.
|
|
The ORM didn't reuse joins for direct foreign key traversals when using
chained filters. For example:
qs.filter(fk__somefield=1).filter(fk__somefield=2))
produced two joins.
As a bonus, reverse onetoone filters can now reuse joins correctly
The regression was caused by the join() method refactor in commit
68847135bc9acb2c51c2d36797d0a85395f0cd35
Thanks for Simon Charette for spotting some issues with the first draft
of the patch.
|
|
This is necessary because get_model() checks are case insensitive, and if the swapable check isn't, the
swappable logic gets tied up in knots with models that are partially swapped out.
Thanks to chris@cogdon.org for the report and extensive analysis, and Preston for his work on the draft patch.
|
|
Thanks to Patryk Zawadzki for the patch.
|
|
Conflicts:
django/db/models/loading.py
django/db/models/options.py
|
|
Thanks Dylan Verheul for the report and Anssi Kääriäinen for the
review.
|
|
|
|
Thanks Valentin Lorentz for the report and the suggested fix.
|
|
This is a rather large refactoring. The "lookup traversal" code was
splitted out from the setup_joins. There is now names_to_path() method
which does the lookup traveling, the actual work of setup_joins() is
calling names_to_path() and then adding the joins found into the query.
As a side effect it was possible to remove the "process_extra"
functionality used by genric relations. This never worked for left
joins. Now the extra restriction is appended directly to the join
condition instead of the where clause.
To generate the extra condition we need to have the join field
available in the compiler. This has the side-effect that we need more
ugly code in Query.__getstate__ and __setstate__ as Field objects
aren't pickleable.
The join trimming code got a big change - now we trim all direct joins
and never trim reverse joins. This also fixes the problem in #10790
which was join trimming in null filter cases.
|
|
Refs #19368, and the fix introduced in 27f8129d64292868f6a328f7bf9a1bed67967ff3.
|
|
Commit was 088d3bc2f84b6b68fee7e5de053b58049bd110e7
|
|
If there are more than one values to compare against and the qs isn't
ordered then assertQuerysetEqual will raise a ValueError.
|
|
Thanks Kit Sunde for the report and Brian Holdefehr for the initial
patch.
|
|
|
|
|
|
Full disclosure and new release forthcoming.
|
|
|
|
Some backends might need special handling for auto-increment values.
This was introduced in 5fa5621f574. Thanks Michael Manfre for spotting
the issue.
|
|
Thanks dloewenherz for the report.
|
|
Also fixes #9045.
|
|
Thanks joebuyer at manycycles.com for the report and Simon Charette
for the review.
|
|
Thanks kujiu for the report and Aymeric Augustin for the review.
|
|
Thanks Simon Charette for the report and the initial patch.
|
|
This was not working properly when ContentFile was initialized with
an unicode string.
Thanks Alexey Boriskin for the report and the test.
|
|
Applied to inlines what ec9d6b1122d did for main fieldsets.
|
|
The failure was caused by using None as a choice for a CharField. To
avoid Oracle's "" <-> NULL handling the field type was changed to
IntegerField.
|
|
|
|
|
|
Fixed #19070: urlize template filter raises exception in some cases
|
|
consistent.
Thanks and at cloverfastfood dot com for the report.
|
|
displayed as selected even if the lookup's first element is not a string.
|
|
Thanks Aymeric Augustin for detecting this regression.
|
|
|
|
Thanks gw 2012 at tnode com for the report.
|