| Age | Commit message (Collapse) | Author |
|
|
|
|
|
You're not allowed to do this after you've made migrations; see ticket
for more details.
|
|
|
|
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.
|
|
Refs #22564.
|
|
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.
|
|
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.
|
|
|
|
Thanks Florian Apolloner for noticing the issue and Aymeric
Augustin for the expertise.
Refs #22540.
|
|
Thanks andrewsg for the report.
|
|
So as the save step is centralized in create(), especially useful
when customizing behavior in subclasses.
Thanks craig.labenz@gmail.com for the report.
|
|
|
|
side effects.
|
|
|
|
|
|
Thanks to chrisedgemon for the report and shaib, akaariai and
timgraham for the review.
|
|
Thanks Tim Graham for the review.
|
|
No more `NewBase` horrors.
Thanks to bendavis78 for his work on merging this into six.
|
|
|
|
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.
|
|
|
|
Refs #22496.
|
|
|
|
Refs #22483
|
|
Fixed #22483 (again).
Forwardport of 5cd6429620 from stable/1.7.x
|
|
Forwardport of 9bbb43dd1a from stable/1.7.x
|
|
Since all state is maintained on the connection at this time and none in
the atomic, it doesn't matter, but it could introduce some subtle bugs
if the implementation changed in the future.
|
|
|
|
This is a security fix; disclosure to follow shortly.
|
|
|
|
|
|
Changed the migration autodetector to remove models last so that FK
and M2M fields will not be left as dangling references. Added a check
in the migration state renderer to error out in the presence of
dangling references instead of leaving them as strings. Fixed a bug
in the sqlite backend to handle the deletion of M2M fields with
"through" models properly (i.e., do nothing successfully).
Thanks to melinath for report, loic for tests and andrewgodwin and
charettes for assistance with architecture.
|
|
This reverts commit 00e3b9a2a992ee0b7288eeeb03e7cbd52ebc6dce.
It's causing a regression when tested with the proxy_model_inheritance tests.
|
|
Changed the migration autodetector to remove models last so that FK
and M2M fields will not be left as dangling references. Added a check
in the migration state renderer to error out in the presence of
dangling references instead of leaving them as strings. Fixed a bug
in the sqlite backend to handle the deletion of M2M fields with
"through" models properly (i.e., do nothing successfully).
Thanks to melinath for report, loic for tests and andrewgodwin and
charettes for assistance with architecture.
|
|
Thanks maciej.pawlisz for the report, and charettes for the review.
|
|
|
|
|
|
|
|
Thanks to @treyhunner and Loïc for their suggestions and review.
|
|
Regression introduced by commit 9777442. Refs #21410.
|
|
|
|
|
|
Thanks intgr for the report.
This commit doesn't include a test because I don't know how to emulate a
database disconnection in a cross-database compatible way.
Also simplified a 'backends' test that was constrained by this problem.
|
|
Refs #15802 -- Reverted #7c657b24 as BaseDatabaseWrapper.close() now
has a proper "finally" clause that may need to preserve self.connection.
|
|
Refs #21202.
|
|
The ticket was originally about two failing tests, which are
fixed by putting their queries in transactions.
Thanks Tim Graham for the report, Aymeric Augustin for the fix,
and Simon Charette, Tim Graham & Loïc Bistuer for review.
|
|
|
|
Thanks Aymeric Augustin for the report and Tim Graham for the review.
|
|
Thanks to linovia for the report.
|