Opened 2 years ago

Closed 2 years 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

Description

After the successful merge of ​#16902, fields support database defaults.
As per Lily Foote's suggestion in a ​comment, we should ask about setting a database default (db_default) in the questioner.

Change History (3)

comment:1 by Bhuvnesh, 2 years ago

Version: 4.2 → dev

comment:2 by Bhuvnesh, 2 years ago

Owner: changed from nobody to Bhuvnesh

comment:3 by Mariusz Felisiak, 2 years ago

Cc: Lily Foote added
Component: Database layer (models, ORM) → Migrations
Resolution: → needsinfo
Status: assigned → closed

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.

Note: See TracTickets for help on using tickets.
Back to Top