Opened 6 years ago

Last modified 6 months ago

#13327 new Cleanup/optimization

FileField/ImageField accessor methods throw unnecessary exceptions when they are blank or null.

Reported by: kevin.howerton@… Owned by: nobody
Component: Database layer (models, ORM) Version: 1.1
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Alex Gaynor)

Many of the accessor methods on the FileField call this method:

    def _require_file(self):
        if not self:
            raise ValueError("The '%s' attribute has no file associated with it." % self.field.name)

This method defeats the blank or null features, and has 0 benefit.

The preferred behavior should be that it raises an error if the field is set, but the file does not exist. However if you try to retrieve a URL or path from a file-field it should return None if the field is Null or if the field is blank. Not sure what the reasoning behind throwing an error here, is but it seems extremely dis-advantageous in practice requiring every image or file-field that can be blank/null to have if/else statement wrapped around it in templates to prevent 500 errors.

Change History (8)

comment:1 Changed 6 years ago by Alex Gaynor

Description: modified (diff)
Needs documentation: unset
Needs tests: unset
Patch needs improvement: unset

Please use preview.

comment:2 Changed 6 years ago by Russell Keith-Magee

Triage Stage: UnreviewedDesign decision needed

This has the potential to be a fairly major change in behavior, so it may not be possible to make this change. However, I can see the point you are making. Determining the right way forward will require some discussion on django-dev.

comment:3 Changed 6 years ago by Apreche

I completely agree that this needs to change.

If you set an Image or File Field to blank/null, then it is expected that there will often be no actual file in the file system. Obviously if there is an operation that requires reading the file from the file system, such as checking the size of the file, then it is obvious that there would be IO errors or file not found exceptions. However, for operations such as getting the path or url, there is no reason to check the file system at all. If the field is null, then these operations should simply return None.

As the submitter has pointed out, the current system requires that you put conditionals around every image field in every template in order to avoid errors that prevent the entire page from loading just because one image is missing. With the suggested change, the pages would load without error, and maybe a few relatively harmless broken images.

comment:4 Changed 5 years ago by Julien Phalip

Severity: Normal
Type: Cleanup/optimization

comment:5 Changed 5 years ago by Thejaswi Puthraya

Component: UncategorizedDatabase layer (models, ORM)
Easy pickings: unset
UI/UX: unset

comment:6 Changed 4 years ago by Anssi Kääriäinen

Triage Stage: Design decision neededAccepted

I agree a change here seems like a good idea. The backwards compatibility needs more investigation than my 2 minute review...

comment:7 Changed 6 months ago by Tim Graham

#26380 is a duplicate.

comment:8 Changed 6 months ago by Mehdy Haghy

any workaround to handle this error?

I get this error in DRF model serializer so I can't suppress it when a FileField is null in database.
considering the model definition, null values should not cause exception but it does

   class Repository(models.Model):
     owner = models.ForeignKey('auth.User', related_name='file_owner')
     file_content= models.FileField(upload_to='repository',null=True, blank=True)
Last edited 6 months ago by Mehdy Haghy (previous) (diff)
Note: See TracTickets for help on using tickets.
Back to Top