| Age | Commit message (Collapse) | Author |
|
|
|
This is a security fix. Disclosure following shortly.
|
|
This is a security fix. Disclosure following shortly.
|
|
Backport of 4cf82e5bcf from master.
|
|
Previously, known related objects overwrote related objects loaded
though select_related. This could cancel the effect of select_related
when it was used over more than one level.
Thanks boxm for the bug report and timo for bisecting the regression.
Backport of f574220f from master
|
|
Thanks Shai for the thorough review.
Backport of fb90b7c from master
|
|
Made explicit lack of microsecond handling by built-in datetime form
fields. Used that explicitness to appropriately nix microsecond
values in bound fields. Thanks Claude Paroz for the review.
Backport of a5de0df58 from master.
|
|
Refactored cache expiry logic for Locmemcache to make consistent across
all places where accessed, and correctly handle None as expiry time.
Backport of 66880e4cd from master.
|
|
|
|
|
|
[1.7.x] Fixed #22588 -- Fix RegexValidator __eq__
|
|
Backport of 99d9fa32 from master
|
|
Oracle and SQL Server don't have exactly the same limitations. It's
worth treating them differently.
Backport of cff59bed from master
|
|
Backport of c70a61eb from master
|
|
Backport of b1432bfc from master
|
|
Backport of fc32e9c0d from master.
|
|
|
|
It's the one shown when the optional integration described in
https://docs.djangoproject.com/en/dev/ref/contrib/admin/#adding-a-password-reset-feature
is used.
Follow-up to commits 6f470650d0 and 1d42a86ec7, together they fix
different small UI regressions after a962286b74.
Refs #21293.
5ea34f3f86 from master.
|
|
|
|
|
|
You're not allowed to do this after you've made migrations; see ticket
for more details.
|
|
Compare parameters instead of re.pattern instances, and add the other
parameters to the comparison. Also add a __ne__ to make assertNotEqual
work properly.
|
|
|
|
|
|
Thanks david.fischer.ch at gmail.com for the report.
Backport of 4492ea5475 from master
|
|
In some cases, this could lead to migrations written with Python 2
being incompatible with Python 3.
Thanks Tim Graham for the report and Loïc Bistuer for the advices.
Backport of da9cf53cb from master.
|
|
Refs #22564.
Backport of 12474dace from master.
|
|
Backport of df60db0e78 from master
|
|
Ordering by reverse foreign key was broken by custom lookups patch
(commit 20bab2cf9d02a5c6477d8aac066a635986e0d3f3).
Thanks to everybody who helped solving this issue. Special thanks to
Trac alias takis for reporting this.
Backport of 3b7c66a3ac from master
|
|
When custom lookups were added, converting the search lookup to use
the new Lookup infrastructure wasn't done.
Some changes were needed to the added test, main change done by
committer was ensuring the test works on MySQL versions prior to 5.6.
Backport of 7131e14d00 from master
|
|
Backport of 5e1f4656b9 from master
|
|
for a default.
Thanks andrewsg for the report.
Backport of 3818d96426 from master
|
|
Thanks ygbo for the report.
Backport of 142c27218 from master.
|
|
values
|
|
prevent side effects.
Backport of e2e4cdba11 from master
|
|
Backport of 45c2d1f5d9 from master.
|
|
|
|
|
|
Thanks to chrisedgemon for the report and shaib, akaariai and
timgraham for the review.
Backport of 24ec9538b7 from master
|
|
Thanks Tim Graham for the review.
Backport of 7c54f8cce from master.
|
|
Backport of d9c272b22f from master
|
|
Backport of 83413c53d2 from master
|
|
No more `NewBase` horrors.
Thanks to bendavis78 for his work on merging this into six.
Backport of a2340ac6d6 from master
|
|
2df7238512 from master.
|
|
This reverts commit 4fdd51b73240bf9c8d9472fcc45df699f0714755.
See the ticket for concerns with this implementation; it will be revisited.
Backport of aabceadd7d from master
|
|
|
|
Backport of 2bcb8bfc8d from master
|
|
Avoided introducing a new regex-based SQL splitter in the migrations
framework, before we're bound by backwards compatibility.
Adapted this change to the legacy "initial SQL data" feature, even
though it's already deprecated, in order to facilitate the transition
to migrations.
sqlparse becomes mandatory for RunSQL on some databases (all but
PostgreSQL). There's no API to provide a single statement and tell
Django not to attempt splitting. Since we have a more robust splitting
implementation, that seems like a good tradeoff. It's easier to add a
new keyword argument later if necessary than to remove one.
Many people contributed to both tickets, thank you all, and especially
Claude for the review.
Refs #22401.
Backport of 8b5b199 from master
|
|
Backport of 3033a71 from master.
Conflicts:
django/db/backends/__init__.py
|
|
after a user password change in the admin.
Thanks ross at servercode.co.uk for the report.
Backport of 9e7f86b890 from master
|