#24104: SQLite schema should to look for internal type of field instead of class
instance when choosing a default for created fields
-------------------------------------+-------------------------------------
Reporter: coldmind | Owner: coldmind
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 1.7
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by claudep:
Old description:
> See alex/django-taggit#285 for example where this issue can be present.
> Some custom related fields can not have a default, but in the same time
> they will be not inheritors of ManyToManyField.
New description:
See [[https://github.com/alex/django-taggit/issues/285|alex/django-
taggit#285]] for example where this issue can be present.
Some custom related fields can not have a default, but in the same time
they will be not inheritors of ManyToManyField.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/24104#comment:3>
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.de5cf8e5da1079eaf0ab615e4c82de25%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
