| Age | Commit message (Collapse) | Author |
|
Since this example was added 15 years ago in a8ccdd0fcd631e8e928ef20547e1fe3e313dc607, the ORM has gained the ability to do the `COUNT(*)` related query, so do it with the ORM to avoid misleading users that raw SQL is only supported from manager methods.
Backport of 59e503b6708d41a44f2aa320272de3e2ecb5d65c from master
|
|
Backport of 550297d20d085bc5a440d905cd3cb2e286588ca8 from master
|
|
Follow up to e1b77238171cc96f4451a06fb4682e2378896238.
Backport of 477c800443d091b5f36be9b5f83ce16c85da5879 from master.
|
|
Backport of c448e614c60cc97c6194c62052363f4f501e0953 from master
|
|
Backport of 284bde3fbe07485d64289e28014a4eada68aef91 from master
|
|
docs example.
Backport of 1b32b2f614c5c45f4a0f270ae7273c2d8e16617b from master
|
|
QuerySet.exclude() in docs.
Backport of 17407eca59b0572228067cdee51433f49a1e0adb from master
|
|
Backport of fcad0b132427847d6db2008f00fbe45a7b45cad3 from master
|
|
Backport of 2d8dcba03aae200aaa103ec1e69f0a0038ec2f85 from master
|
|
__contained_by lookups on SQLite.
The current implementation works only for basic examples without
supporting nested structures and doesn't follow "the general principle
that the contained object must match the containing object as to
structure and data contents, possibly after discarding some
non-matching array elements or object key/value pairs from the
containing object".
Backport of ba691933cee375195c9c50f333dd4b2a3abbb726 from master.
|
|
Oracle.
The current implementation works only for basic examples without
supporting nested structures and doesn't follow "the general principle
that the contained object must match the containing object as to
structure and data contents, possibly after discarding some
non-matching array elements or object key/value pairs from the
containing object".
Backport of 02447fb133b53ec7d0ff068cc08f06fdf8817ef7 from master
|
|
Backport of 5ef6f626347f9ea13915f3cf5b8b045c5b42b102 from master
|
|
Backport of d88952142bff1c0283a929749fb64c53d07ad91e from master
|
|
Backport of 06c8565a4650b359bdfa59f9707eaa0d1dfd7223 from master
|
|
Backport of 682b295c6c3f5a2182bdc8192f0b8b65610fe4b1 from master
|
|
Backport of 494ba27b5fe14e42e815edde6bd4a1216b29c935 from master
|
|
Backport of 5af17babb0f895cf129fdeee92548d2ac12e78e2 from master
|
|
Backport of a9337b4add01e50ed8ff8d3ef44099a08cba475c from master
|
|
Thanks to Adam Johnson, Carlton Gibson, Mariusz Felisiak, and Raphael
Michel for mentoring this Google Summer of Code 2019 project and
everyone else who helped with the patch.
Special thanks to Mads Jensen, Nick Pope, and Simon Charette for
extensive reviews.
Co-authored-by: Mariusz Felisiak <felisiak.mariusz@gmail.com>
|
|
comments.
|
|
|
|
|
|
|
|
|
|
|
|
models.BaseManager.
|
|
|
|
|
|
for self-referential ManyToManyField.
Follow up to 87b1ad6e7351464c60e751b483d9dfce3a2d3382.
|
|
|
|
|
|
It's slightly aggressive and doesn't explain itself.
|
|
|
|
|
|
Make sure that AuthRouter includes ContentType in the same database.
|
|
It was barely documented without pointers at its defining location and
was abused to prevent misuse of the QuerySet field deferring feature.
|
|
the database optimization docs.
|
|
|
|
Follow up to 97d3321e89c8d4434927bdbc308db1ccffa99d3b.
|
|
|
|
deferred fields.
This is not true since 7f51876 removed the necessity of creating
proxy model classes at runtime for each deferred field sets.
|
|
Per deprecation timeline.
|
|
|
|
involved difficulty.
This patch does not remove all occurrences of the words in question.
Rather, I went through all of the occurrences of the words listed
below, and judged if they a) suggested the reader had some kind of
knowledge/experience, and b) if they added anything of value (including
tone of voice, etc). I left most of the words alone. I looked at the
following words:
- simply/simple
- easy/easier/easiest
- obvious
- just
- merely
- straightforward
- ridiculous
Thanks to Carlton Gibson for guidance on how to approach this issue, and
to Tim Bell for providing the idea. But the enormous lion's share of
thanks go to Adam Johnson for his patient and helpful review.
|
|
These classes can serve as a base class for user enums, supporting
translatable human-readable names, or names automatically inferred
from the enum member name.
Additional properties make it easy to access the list of names, values
and display labels.
Thanks to the following for ideas and reviews:
Carlton Gibson, Fran Hrženjak, Ian Foote, Mariusz Felisiak, Shai Berger.
Co-authored-by: Shai Berger <shai@platonix.com>
Co-authored-by: Nick Pope <nick.pope@flightdataservices.com>
Co-authored-by: Mariusz Felisiak <felisiak.mariusz@gmail.com>
|
|
|
|
|
|
|
|
|
|
migrations.
|