| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
While deferring many-to-many and GFK has no effect, the previous
implementation of QuerySet.defer() ignore them instead of crashing.
Regression in b3db6c8dcb5145f7d45eff517bcd96460475c879.
Thanks Paco Martínez for the report.
|
|
|
|
| |
Regression in 5c23d9f0c32f166c81ecb6f3f01d5077a6084318.
|
|
|
|
|
|
|
|
| |
Special thanks to Hannes Ljungberg for finding multiple implementation
gaps.
Thanks also to Simon Charette, Adam Johnson, and Mariusz Felisiak for
reviews.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Proper escaping of % in string literals used when defining constaints
was attempted (a8b3f96f6) by overriding quote_value of Postgres and
Oracle schema editor. The same approach was used when adding support for
constraints to the MySQL/MariaDB backend (1fc2c70).
Later on it was discovered that this approach was not appropriate and
that a preferable one was to pass params=None when executing the
constraint creation DDL to avoid any form of interpolation in the first
place (42e8cf47).
When the second patch was applied the corrective of the first were not
removed which caused % literals to be unnecessary doubled. This flew
under the radar because the existings test were crafted in a way that
consecutive %% didn't catch regressions.
This commit introduces an extra test for __exact lookups which
highlights more adequately % doubling problems but also adjust a
previous __endswith test to cover % doubling problems (%\% -> %%\%%).
Thanks Thomas Kolar for the report.
Refs #32369, #30408, #30593.
|
| |
|
|
|
|
| |
It's also supported on SQLite 3.35+ and MariaDB 10.5+.
|
|
|
|
| |
when optimizing migrations.
|
| |
|
|
|
|
|
|
|
|
|
| |
Oracle.
Regression in 09ffc5c1212d4ced58b708cbbf3dfbfb77b782ca.
Thanks Michael Smith for the report.
This also reverts commit 1e4da439556cdd69eb9f91e07f99cf77997e70d2.
|
| |
|
|
|
|
|
|
|
|
| |
Meta.indexes/index_together when optimizing migrations.
This makes squashing migrations an available path for changing
Meta.index_together, which is deprecated, to Meta.indexes.
Follow up to f81032572107846922745b68d5b7191058fdd5f5.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QuerySet.update_or_create() with MyISAM storage engine.
QuerySet.update_or_create() uses nested atomic to handle possible
integrity errors taking savepoints as way to mark back the connection
as usable. Savepoints are not returned when
uses_savepoints/can_release_savepoints feature flags are set to False.
As a consequence, QuerySet.update_or_create() assumed the outer atomic
block is tainted and raised TransactionManagementError.
This commit partly reverts 331a460f8f2e4f447b68fba491464b68c9b21fd1.
Thanks gatello-s for the report.
|
|
|
|
| |
width/height fields.
|
| |
|
| |
|
|
|
|
| |
self-referential subqueries if supported.
|
|
|
|
| |
It was a copy of sql.Query._add_q that avoided JOIN updates.
|
|
|
|
|
| |
It's unused now that the specialized FilteredRelation.as_sql logic is
no more.
|
|
|
|
|
|
|
|
|
|
|
| |
The previous implementation resolved condition at Join compilation time
which required introducing a specialized expression resolving mode to
alter the join reuse logic solely during that phase.
FilteredRelation.condition is now resolved when the relation is first
referenced which maintains the existing behavior while allowing the
removal of the specialized resolving mode and address an issue where
conditions couldn't spawn new joins.
|
|
|
|
| |
when db_collation is set in related field.
|
|
|
|
| |
get_joining_columns()/get_reverse_joining_columns() methods.
|
|
|
|
| |
relation on PostgreSQL.
|
|
|
|
|
|
| |
existing database connection on PostgreSQL.
Regression in 09ffc5c1212d4ced58b708cbbf3dfbfb77b782ca.
|
| |
|
|
|
| |
Regression in 6a2165816394ab4bb259f6171e82417e098e97a6.
|
|
|
|
|
|
| |
PostgreSQL.
Regression in 09ffc5c1212d4ced58b708cbbf3dfbfb77b782ca.
|
|
|
|
|
|
|
|
| |
Regression in 59bea9efd2768102fc9d3aedda469502c218e9b7.
Refs #28477.
Thanks Ian Cubitt for the report.
|
|
|
|
|
|
| |
Thanks Andrew Cordery for the report.
Regression in b3db6c8dcb5145f7d45eff517bcd96460475c879.
|
|
|
|
| |
Thanks Roman Odaisky for the report.
|
|
|
|
|
| |
hiding clause-less exceptions.
Regression in 3cafb783f3f711c7413ba2b8d7c8ff750bd4d6e1.
|
|
|
| |
Regression in ce6230aa976e8d963226a3956b45a8919215dbd8.
|
|
|
| |
Bug in cd1afd553f9c175ebccfc0f50e72b43b9604bd97.
|
|
|
|
|
| |
While the add_fields() call from set_values() does trigger validation it
does so after annotations are masked resulting in them being excluded
from the choices of valid options surfaced through a FieldError.
|
|
|
|
|
|
| |
QuerySet.values()/values_list() on compound queries.
Co-authored-by: Matthias Kestenholz <mk@feinheit.ch>
|
|
|
|
| |
form fields.
|
| |
|
| |
|
|
|
|
| |
annotations.
|
| |
|
|
|
|
|
|
| |
index/constraint on new foreign key.
Thanks Simon Charette and David Wobrock for reviews.
|
|
|
|
|
| |
This prevents a sqlite3 crash and address a potential DDoS vector on
PostgreSQL caused by full-table-scans on overflows.
|
| |
|
|
|
|
|
|
| |
passed.
This reverts 340eaded4e30cf25bcd4e9781d33a617fe9c0f84.
|
|
|
|
|
| |
This also fixes test_rename_field_with_check_to_truncated_name() on
MariaDB 10.5.2+ as ALTER TABLE ... RENAME COLUMN statement doesn't
rename inline constraints.
|
|
|
|
|
|
|
|
| |
window expression.
Regression in f387d024fc75569d2a4a338bfda76cc2f328f627.
Co-authored-by: Jannis Vajen <jvajen@gmail.com>
|
|
|
|
|
|
| |
Regression in 278881e37619278789942513916acafaa88d26f3 caused by a lack
of expression copying when an OrderBy expression is explicitly provided.
Thanks Jannis Vajen for the report and regression test.
|
| |
|
|
|
|
|
|
|
|
| |
CheckConstraint if not supported.
The new logic mirrors the logic in SchemaEditor._delete_check_sql()
added in 68ef274bc505cd44f305c03cbf84cf08826200a8.
Thanks Tim Graham for the report.
|
|
|
|
| |
BaseConstraint and subclasses.
|