#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 Mariusz Felisiak):
> The same could apply to migrations. Since there's only one possible
value for "no data" for the existing rows, it's probably better to use
that than to ask for that value or crash.
It's not the same to use the empty string for a new row and to update
**all existing** rows without asking for a value. With your proposition we
would remove an important feature from migrations and we wouldn't give
users a chance to decide on their own, which they have when creating a new
object.
Again, please start a discussion on DevelopersMailingList if you don't
agree.
--
Ticket URL: <https://code.djangoproject.com/ticket/32799#comment:4>
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.f3e1d5c8906adc1adf2dd9f6a0c8eb65%40djangoproject.com.
