| Age | Commit message (Collapse) | Author |
|
|
|
|
|
Reduces the possibility of circular imports.
|
|
favor of databases.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Thanks Steven Ganz for the detailed report.
|
|
Refs #11964.
Thanks Scott Stevens for testing this upcoming feature and the report.
|
|
|
|
|
|
|
|
|
|
arguments.
Also renamed the `constraint` argument to `check` to better represent which
part of the constraint the provided `Q` object represents.
|
|
|
|
Also fixed test failures if sqlparse isn't installed.
|
|
|
|
tilde or underscore.
Regression in 29150d5da880ac1db15e47052330790cf1b802d2.
|
|
|
|
|
|
dots.
Thanks Sudhanshu Mishra for the initial patch and Tim Graham for the review.
|
|
|
|
Refs #29600 -- Removed usage of django.utils.datetime_safe in migrations.
|
|
The issue was fixed as a side effect of implementing RemoveField's reduction
of DeleteModel to a DeleteModel in ad82900ad94ed4bbad050b9993373dafbe66b610.
|
|
|
|
|
|
This should alleviate the side effects of disabling the AlterFooOperation
reduction with RemoveField to fix refs #28862 during migration squashing
because CreateModel can perform a reduction with RemoveField.
Thanks Nick Pope for the review.
|
|
AlterFooTogether operations cannot be swapped with RemoveField operations on
the same model as they could be removing the the same field as well.
Since AlterFooTogether operations don't track what their previous value was,
it's impossible to determine whether or not the optimization is safe so the
only way to proceed is to disable the optimization.
Thanks Ramiro Morales for the in-depth analysis of the issue.
Refs #24828
|
|
Thanks Raphael Gaschignard for the suggestion.
|
|
|
|
|
|
|
|
Thanks Ed Morley from Mozilla for the tests.
|
|
Operations can only be optimized through if they don't reference any of the
state the operation they are compared against defines or alters, so it's
safe to reverse the order.
|
|
An explicit intermediary many-to-many relationship must declare forward and
reverse foreign keys. The original issue was in the autodetector as these
operations shouldn't have been generated in this order in the first place
which is tested by AutodetectorTests.test_create_with_through_model.
|
|
|
|
|
|
|
|
|
|
Thanks MyungSeKyo for the report and the initial patch.
|
|
|
|
|
|
|
|
|
|
RenameField.
Regression in 45ded053b1f4320284aa5dac63052f6d1baefea9.
|
|
|