#25756: ArrayField does not work with FileField
----------------------------------+------------------------------------
Reporter: Anthony Dong | Owner: (none)
Type: Bug | Status: new
Component: contrib.postgres | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by Alex):
Hello.
I tried to replicate this bug last night, following the posted
instructions.
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
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/25756#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/064.32bb7158c4b1ab8cdaf61ee23abdf193%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
