Opened 9 years ago
Last modified 9 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 )
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 by , 9 years ago
| Has patch: | set |
|---|---|
| Patch needs improvement: | set |
| Severity: | Normal → Release blocker |
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 9 years ago
| Summary: | Refs #23987 - SQLite schema should to look for internal type of field instead of class instance when choosing a default for created fields → SQLite schema should to look for internal type of field instead of class instance when choosing a default for created fields |
|---|
comment:3 by , 9 years ago
| Description: | modified (diff) |
|---|
Note:
See TracTickets
for help on using tickets.
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.