#18501: Custom fields as foreign keys fix
-------------------------------------+-------------------------------------
Reporter: msopacua | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: RelatedField | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* status: new => closed
* resolution: => needsinfo
Comment:
As the sample project uses the deprecated `SubfieldBase` class to
construct the custom field, I am going to close this ticket as
"needsinfo". I suspect this issue may have been fixed since this ticket
was created as `UUIDField` has been introduced into core and we fixed
several related bugs.
Feel free to reopen with more details if it's still an issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/18501#comment:8>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.641f53a2f2cb2444685f4fe5965a47c2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
