#32799: Inconsistency regarding the default value of CharField
-------------------------------+--------------------------------------
Reporter: Adam Sołtysik | Owner: nobody
Type: New feature | Status: closed
Component: Migrations | Version: 3.2
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Adam Sołtysik):
> With your proposition we would remove an important feature from
migrations and we wouldn't give users a chance to decide on their own
Actually, my proposition is just to make migrations use the same default
value that objects use, when there is no explicit default value given. The
questioner could still work the same if that's more consistent with other
fields. My use case was a migration edited by hand, which crashed due to
nulls, when I expected it to use empty strings.
--
Ticket URL: <https://code.djangoproject.com/ticket/32799#comment:5>
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/065.e7cd9a59850ef045d6a0015dad6ea1dd%40djangoproject.com.
