Opened 17 months ago
Closed 17 months ago
#34637 closed New feature (needsinfo)
Add support for database defaults in questioner.
Reported by: | Bhuvnesh | Owned by: | Bhuvnesh |
---|---|---|---|
Component: | Migrations | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Lily Foote | Triage Stage: | Unreviewed |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Change History (3)
comment:1 by , 17 months ago
Version: | 4.2 → dev |
---|
comment:2 by , 17 months ago
Owner: | changed from | to
---|
comment:3 by , 17 months ago
Cc: | added |
---|---|
Component: | Database layer (models, ORM) → Migrations |
Resolution: | → needsinfo |
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
I'm not sure what that will change 🤔. In migrations we're asking for one-time temporary default value that we can set on existing rows, not for a permanent default value, so the current message sounds fine to me. If a simple default value doesn't work for users, they can choose the 3rd option: "Quit and manually define a default value in models.py." and define
default
/db_default
in models.