#5726 closed Cleanup/optimization (fixed)
Document that inspectdb doesn't detect default values
Reported by: | anonymous | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Normal | Keywords: | inspectdb |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Testing with MySQL, no default values are used from the table definition.
Attachments (1)
Change History (12)
comment:1 by , 17 years ago
Triage Stage: | Unreviewed → Someday/Maybe |
---|
comment:2 by , 14 years ago
Component: | django-admin.py inspectdb → Core (Management commands) |
---|
comment:3 by , 14 years ago
Severity: | → Normal |
---|---|
Type: | → New feature |
comment:4 by , 13 years ago
Easy pickings: | unset |
---|---|
UI/UX: | unset |
comment:5 by , 13 years ago
Keywords: | inspectdb added |
---|
comment:6 by , 10 years ago
Component: | Core (Management commands) → Documentation |
---|---|
Summary: | inspectdb should recognize default values → Document that inspectdb doesn't detect default values |
Triage Stage: | Someday/Maybe → Accepted |
Type: | New feature → Cleanup/optimization |
Translating database level defaults into model field defaults isn't functionally equivalent and given that Django doesn't translate the model field default
option into a database level default, I think it would be inconsistent to do a conversion in the other direction.
However, we can document the reason that this isn't supported.
by , 10 years ago
comment:7 by , 10 years ago
Has patch: | set |
---|
comment:8 by , 10 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
comment:9 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
With PostgreSQL too.