#34820: Change the properties of ForeignObject object, such as blank, null, and
execute migrate to report an error
-------------------------------------+-------------------------------------
Reporter: RelaxedDong | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by RelaxedDong):
Replying to [comment:3 Mariusz Felisiak]:
> I'm not sure how to you reach a field without a `column` in migrations.
I don't think you've explained the issue in enough detail to confirm a bug
in Django, can you provide a sample project or test case that reproduces
the issue?
I submitted my case code and process
--
Ticket URL: <https://code.djangoproject.com/ticket/34820#comment:6>
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/0107018a738057eb-1250b473-c8d6-4640-bf98-65946774ba1e-000000%40eu-central-1.amazonses.com.