#34608: Migrations generates code that it can't execute
-------------------------------+--------------------------------------
     Reporter:  Michael        |                    Owner:  nobody
         Type:  Uncategorized  |                   Status:  closed
    Component:  Migrations     |                  Version:  4.0
     Severity:  Normal         |               Resolution:  invalid
     Keywords:                 |             Triage Stage:  Unreviewed
    Has patch:  0              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+--------------------------------------
Changes (by Natalia Bidart):

 * keywords:  make migrations =>
 * status:  new => closed
 * resolution:   => invalid


Comment:

 Hello!

 First of all, please note that you are using a version of Django that is
 no longer supported (4.0.1).
 Secondly, the error seems to be caused by either:

 1. a possible misconfiguration/bug in your code, or
 2. the result from squashing the migrations is somehow invalid.

 For the first case, the recommended approach is to first ensure whether
 the error you are getting is a bug in Django itself, or not in your code.
 To do that, you can follow
 [https://docs.djangoproject.com/en/4.2/internals/contributing/bugs-and-
 features/#reporting-bugs the bug reporting guide] and seek help in the
 Django User channels to evaluate whether your problem is caused by a
 configuration issue.

 For the second case, we would need a minimal example of two working
 migrations and their minimal models that, when squashed, would generate
 the invalid result. It's important to try to narrow the models and
 migrations to the bare minimum that triggers the issue, and that what's
 shared in the bug is fully functional. At the very least we'd need the
 migrations that were squashed down to the result you pasted in this
 report.

 Closing this ticket as invalid for now, but if you find a concrete bug in
 Django itself or if you can provide a reproducer for the faulty squashed
 migration, please let us know and we'll analyze this further. Thanks!

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34608#comment:2>
Django <https://code.djangoproject.com/>
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701886dae03be-dae0115f-6df9-488b-81b0-c3e2a58e3da1-000000%40eu-central-1.amazonses.com.

Reply via email to