﻿id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
652	An option to upload files into database would be a great alternative to filesystem uploads.	cygnus@…	Adrian Holovaty	"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"	enhancement	closed	Database layer (models, ORM)	dev	normal	wontfix	upload	cygnus@… dev@…	Design decision needed	0	0	0	0	0	0
