ArrayField does not work with FileField

[Anthony Dong]

When using the following models.py definition :

from django.contrib.postgres.fields import ArrayField

class Album(models.Model):
    pictures = ArrayField(models.FileField(upload_to='files'))

And the following admin.py

from django.contrib.postgres.forms import SplitArrayField
class AlbumForm(forms.ModelForm):
    pictures = SplitArrayField(forms.FileField(), size=2)
    class Meta:
        model = models.Album
        fields = '__all__'

class AlbumAdmin(admin.ModelAdmin):
    form = AlbumForm

admin.site.register(models.Album, AlbumAdmin)

Creating a new Album in the Django admin works, but:

• Files are not getting saved
• Retrieving a FieldFile is impossible:

  python manage.py shell
  from my_app.models import Album
  Album.objects.get().pictures == [u'filename.png', u'filename2.png']
  

I would have expected a list of FieldFiles.

[Tim Graham]

I'm not sure to what extent we can fix this, but if not, we can document the limitation or try to add a helpful error message indicating that it's unsupported.

[Riccardo Di Virgilio]

Hi, I'm implementing an ArrayField and I can attach a "working" and very dirty implementation.

So far I found several problems:

1. If you use a FileField this field is using a descriptor to transform strings into File objects (instead of to_python), which is why the array field is always returning strings and not file objects.

2. The save method of FileField is setting the instance file attribute to a file, which in this case is wrong because it should be a list of files.

3. the pre save method in file field is the one that is actually saving the file, since ArrayField is not calling the super of that, this cannot work.

[Nikolai Ryzhkov]

Hi. I've faced this limitation.

After quick review of FileField and ArrayField I found out that this problem can't be resolved without redesign of ArrayField.
We can't append a FileField's instance to list which is a instance of ArrayField. The FileField's instance requires access to field (It should get upload_to and storage). So we should have wrapper under list which will be know his field first.

[Jack]

How is this situation in 1.11? Is it still not working?

[Alex]

Replying to Jack:

How is this situation in 1.11? Is it still not working?

I tried to replicate this bug last night; I followed the original posted instructions in this ticket.

It appears to still be a valid bug, although difficult to say for sure without a thorough test.

Tested relevant software versions:
Django version 2.0
Python version 3.6
Postgresql version 10.3

Steps followed to reproduce as described in this ticket.

Results observed consistent with those described in this ticket:

Files are not getting saved in any observable place
Retrieving a FileField is impossible:

(same as previously reported)

    python manage.py shell
    >>> from my_app.models import Album
    >>> Album.objects.get().pictures == [u'filename.png', u'filename2.png']
    >>> true

Album object appears to incorrectly contain filename strings rather than expected <FieldFile: files/filename.png> FieldFile type data.

[johnthagen]

Bug still exists in 2.2.10. This transitively affects users of Django REST Framework who try to serialize multiple Base64 files into a ListField:

# models.py
from django.contrib.postgres.fields import ArrayField

class Store(Model):
    files = ArrayField(models.FileField(upload_to='files', null=True, blank=True))

# serializers.py
from drf_extra_fields.fields import Base64ImageField
from rest_framework.fields import ListField

class StoreSerializer(ModelSerializer):
    datasheets = ListField(child=Base64ImageField())

    class Meta:
        model = Store
        fields = '__all__'

# views.py
class StoreViewSet(ModelViewSet):
    queryset = Store.objects.all()
    serializer_class = StoreSerializer

Doing this results in incorrect results, returning null instead of a file path and failing to save the file. Would be really nice if it was possible to fix this.

[Mariusz Felisiak]

Replying to johnthagen:

Doing this results in incorrect results, returning null instead of a file path and failing to save the file. Would be really nice if it was possible to fix this.

Feel-free to prepare a patch.

[Laszlo Marai]

I've just ran into this (after trying to fix a 3rd party ArrayList field+widget for the admin site). What I've found, after hours of debugging is basically identical to Ricardo's comment from 5 years ago. I understand that this is a larger change and probably not too many people are affected anyway, but could someone please update the documentation to save time for anyone who may have the idea of using ArrayListField with a FileField?

Currently, it says (under the base_field section):

Most field types are permitted, with the exception of those handling relational data (ForeignKey, OneToOneField and ManyToManyField).

This (the exceptions) should be extended with ArrayField. Though, it would probably be better to list the ones that are known to work with it.

[Claude Paroz]

​PR to document the limitation.

[GitHub <noreply@…>]

In a46dfa87:

Refs #25756 -- Doc'd inability to use file fields with PostgreSQL ArrayField.

[Mariusz Felisiak <felisiak.mariusz@…>]

In 1fd79033:

[4.1.x] Refs #25756 -- Doc'd inability to use file fields with PostgreSQL ArrayField.

Backport of a46dfa87d0ba690125be98f7f1b77062a1794fdc from main