#23679: varchar(255) converted into varchar(255) NOT NULL after inspectdb
followed
by migrate
-------------------------------------+-------------------------------------
Reporter: paulcdejean | Owner: nobody
Type: Bug | Status: new
Component: Core (Management | Version: 1.7
commands) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by carljm):
Given those two choices, I'm in favor of the second option as well, though
I don't even think the comment is really necessary.
I think Django's advice re null CharFields is questionable, but even if we
accept that advice, a `CharField(null=True)` is still a valid, functional
configuration, and there is no reason for `inspectdb` to prohibit it and
intentionally generate models that don't match the source database.
--
Ticket URL: <https://code.djangoproject.com/ticket/23679#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.90f42bd1e0af4cf8675b59ad1b58a6c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
