#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):
> Except for the fact that currently blank=True can be used with char
fields instead of a default value for the migration to work properly, even
though blank parameter is said in the documentation to matter for form
validation only.
I've found there was already a ticket about this: #27197, and a discussion
on the mailing list: https://groups.google.com/g/django-
developers/c/upbDlFgtCHs/discussion, but without any resolution.
--
Ticket URL: <https://code.djangoproject.com/ticket/32799#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/065.37aaf133d7cd74947677ac5ce56ce56f%40djangoproject.com.
