Opened 16 years ago

Last modified 2 months ago

#10244 assigned

FileFields can't be set to NULL in the db — at Initial Version

Reported by: oyvind Owned by: nobody
Component: Database layer (models, ORM) Version: 1.0
Severity: Normal Keywords: filefield NULL empty
Cc: Adam Zapletal Triage Stage: Accepted
Has patch: yes Needs documentation: yes
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Saving FileFields with a none value sets the field to a empty string in the db and not NULL as it should.

According to the ticket's flags, the next step(s) to move this issue forward are:

  • To write documentation for the patch, then uncheck "Needs documentation" on the ticket.

  • If creating a new pull request, include a link to the pull request in the ticket comment when making that update. The usual format is: [https://github.com/django/django/pull/#### PR].

Change History (0)

Note: See TracTickets for help on using tickets.
Back to Top