#34637: Add support for database defaults in questioner.
-----------------------------+--------------------------------------
Reporter: Bhuvnesh | Owner: Bhuvnesh
Type: New feature | Status: closed
Component: Migrations | Version: dev
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Changes (by Mariusz Felisiak):
* cc: Lily Foote (added)
* resolution: => needsinfo
* status: assigned => closed
* component: Database layer (models, ORM) => Migrations
Comment:
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/34637#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701889405e82b-1b9c286e-7fa7-4985-a71d-13c076c0a8a7-000000%40eu-central-1.amazonses.com.
