Opened 8 years ago

Last modified 8 years ago

#24104 closed Cleanup/optimization

SQLite schema should to look for internal type of field instead of class instance when choosing a default for created fields — at Version 3

Reported by: Andriy Sokolovskiy Owned by: Andriy Sokolovskiy
Component: Database layer (models, ORM) Version: 1.7
Severity: Release blocker Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Claude Paroz)

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.

Change History (3)

comment:1 Changed 8 years ago by Tim Graham

Has patch: set
Patch needs improvement: set
Severity: NormalRelease blocker
Triage Stage: UnreviewedAccepted

comment:2 Changed 8 years ago by Tim Graham

Summary: Refs #23987 - SQLite schema should to look for internal type of field instead of class instance when choosing a default for created fieldsSQLite schema should to look for internal type of field instead of class instance when choosing a default for created fields

I haven't looked into this issue, but just wanted to note that we also have the Field.many_to_many attribute (though it's new in 1.8) which may be appropriate for this.

comment:3 Changed 8 years ago by Claude Paroz

Description: modified (diff)
Note: See TracTickets for help on using tickets.
Back to Top