Changes between Version 1 and Version 3 of Ticket #27858


Ignore:
Timestamp:
Feb 19, 2017, 6:07:32 AM (8 years ago)
Author:
Marti Raudsepp
Comment:

D'oh! You are right of course, it was a logic error in my allow_migrate method. That fixes my use case, thanks!

However, I still think the patch has some merit. It has always felt wrong to me that operations that should be entirely read-only, like makemigrations or runserver, go and start creating tables. Do you agree?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #27858 – Description

    v1 v3  
    55Django has always had the problem of being "opinionated", meaning there's often fighting involved if you don't exactly follow The True Django Way. :) This patch is a small step in making Django more flexible.
    66
    7 PS: I understand that version 1.11 is already in a feature freeze, but is there aaaaany chance of getting this patch in there?
     7~~PS: I understand that version 1.11 is already in a feature freeze, but is there aaaaany chance of getting this patch in there?~~
Back to Top