An option to upload files into database would be a great alternative to filesystem uploads.

[cygnus@…]

The filesystem-only method of uploading files for meta.FileField and meta.ImageField is understandable, but a method of using FileFields and ImageFields to upload into a database (as BLOBs, large objects, BYTEA values, etc.) would be extremely useful when filesystem storage is not desirable. Is this feasible? Some thoughts are:

• Use kwargs to the ImageField and FileField constructors to specify the image storage backend
• If storing files in the database, create a table (say, a "binary storage table") as part of django-admin.py sqlall that stores the files in a format that is appropriate for the database backend (e.g. BLOB for MySQL, BYTEA or large object for PostgreSQL)
• User-defined fields that store images or files actually store an ID referring to a record in the binary storage table
• Database abstraction layers will need to implement some methods to use for storing and loading files from the database so ImageField and FieldField objects can retrieve them in a general way

[Adrian Holovaty]

Duplicate of #250.

[cygnus@…]

This ticket's topic is similar to #250, but it's different in a pretty big way; can we dicuss?

[hugo]

Maybe we could have something like abstract "filestorages". The default one would be like what django does now - storing in the filesytem below MEDIA_ROOT. FileFields could get a filestorage=xxxx keyword to switch to some other filestorage. A file storage would need hooks to save a file and to return the files URL - a database filestorage would need to reference a view function, of course, as the database isn't directly accessible by the webserver.

[Adrian Holovaty]

Duplicate of #250.

[Adrian Holovaty]

Milestone Version 0.93 deleted

[anonymous]

fdfdfd

[Noah Slater <nslater@…>]

This is NOT a duplicate of #250 as that is marked as a duplicate of #2417 and that is specifically stated to not apply to FileField and ImageField:

​http://code.djangoproject.com/ticket/2417#comment:5

[Simon G. <dev@…>]

Please see discussion at ​http://groups.google.com/group/django-developers/t/266565a23b765ea2

[Simon G. <dev@…>]

Given the discussion on the list above, I've marked this as wontfix for the time being. It shouldn't be too hard to implement yourself if you do need this functionality, however, if someone wants to write up a proposal / initial code for this, then please do so and re-open.