#34820: Change the properties of ForeignObject object, such as blank, null, and
execute migrate to report an error
-------------------------------------+-------------------------------------
Reporter: puc_dong | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: invalid
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 puc_dong):
Replying to [comment:8 Mariusz Felisiak]:
> `ForeignObject` is an abstraction level, not a proper model field. You
should use `models.ForeignKey`. If you're having trouble understanding how
Django works, see TicketClosingReasons/UseSupportChannels for ways to get
help.
We do not need to create a foreign key, we have used ForeignObject and
currently only need to perform queries. Should this field not be generated
in the migration record for the first time?
--
Ticket URL: <https://code.djangoproject.com/ticket/34820#comment:9>
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/0107018a73b6a501-1939ebe4-6598-428d-b219-439bcace99a8-000000%40eu-central-1.amazonses.com.
