Re: [Django] #27155: makemigrations --no-check-consistency command line argument

2016-08-30 Thread Django 
#27155: makemigrations --no-check-consistency command line argument
-+-
 Reporter:  sjoerdjob|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.10
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  makemigrations,  | Triage Stage:
  check_consistent_history   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * status:  new => closed
 * resolution:   => wontfix
 * needs_tests:   => 0
 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization


Comment:

 It's a non-trivial amount of work to add and documentation a new option
 and then to deprecate it if we fix things later, so I'm not in favor. If
 it's truly a blocker for a project, a workaround is to add your own
 `makemigrations` command without the consistency check, so the issue is
 really not that critical.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.0d3c34f66388c1a9d8d449927860026b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27155: makemigrations --no-check-consistency command line argument

2016-08-30 Thread Django 
#27155: makemigrations --no-check-consistency command line argument
-+-
 Reporter:   |  Owner:  nobody
  sjoerdjob  |
 Type:   | Status:  new
  Uncategorized  |
Component:   |Version:  1.10
  Migrations |   Keywords:  makemigrations,
 Severity:  Normal   |  check_consistent_history
 Triage Stage:   |  Has patch:  0
  Unreviewed |
Easy pickings:  0|  UI/UX:  0
-+-
 There are a number of edge-cases for makemigrations where it fails in 1.10
 while it did not fail in 1.9.

 To quote Tim Graham in #27142:

 > I'm beginning to think that makemigrations shouldn't have this check in
 the first place due to the many issues that have been reported (#27054,
 #27110, #27141) and the more and more complexity that seems needed to add
 to fix it. Other opinions welcome. In my view, the most natural thing to
 do after creating a migration is to apply it, so it doesn't seem like
 delaying the check from makemigrations to migrate would have a huge
 drawback.

 I propose that we add a command line argument `--no-check-consistent-
 history` (or something similar, bikeshed away!) which skips the calls to
 `check_consistent_history`.

 To me it seems like this should be possible to add in the next release and
 takes the pressure off fixing the corner-cases a bit to make sure we can
 come up with a good solution.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.cd52ed211f4b72d00a8c29b34b2db258%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.