#10244: FileFields can't be set to NULL in the db
-------------------------------------+-------------------------------------
Reporter: oyvind | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: filefield NULL | Triage Stage: Accepted
empty |
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Old description:
> Saving FileFields with a none value sets the field to a empty string in
> the db and not NULL as it should.
New description:
Hi,
--
Comment (by Raffaele Salmaso):
Hi all, what is the status of this ticket?
`FileField` behaviour is not really clear right now and `flake8-django`
just made a change to allow `FileField(null=True)` (see
https://github.com/rocioar/flake8-django/issues/82), which seems wrong to
me.
I'm for option 2 `make FileField behave exactly like CharField wrt.
null`.
--
Ticket URL: <https://code.djangoproject.com/ticket/10244#comment:17>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.f0e18e86ce9921ae90aee6c2860fc22c%40djangoproject.com.
