Uploading a file in any application is pretty much a trivial process. I found a really nice blog over here<\/p>\n\n\n\n
How to Upload Files With Django
Updated at Aug 1, 2016: As suggested by@fapolloner, I’ve removed the manual file handling. Updated the example using…simpleisbetterthancomplex.com<\/a><\/p><\/blockquote>\n\n\n\nBut we had a more complex requirement, where there were various entities which required files to be associated with them as an attachments and that too of different types like video, audio or text. One obvious way is to create a separate relation for each of the file type. But we were looking for something more sophisticated.<\/p>\n\n\n\n
Django ContentTypes<\/h2>\n\n\n\n
Django supports a special framework called contenttypes which allows us to include generic foreign keys in our model.<\/p>\n\n\n\n
A normal ForeignKey<\/a> can only “point to” one other model, which means that if the TaggedItem model used a ForeignKey<\/a> it would have to choose one and only one model to store tags for. The contenttypes application provides a special field type (GenericForeignKey) which works around this and allows the relationship to be with any model:<\/p>\n\n\n\n
Below is the example code for Models with contenttype<\/p>\n\n\n\n
There are three parts to setting up a GenericForeignKey<\/a>:<\/p>\n\n\n\n
- Give your model a ForeignKey<\/a> to ContentType<\/a>. The usual name for this field is content_type.<\/li>
- Give your model a field that can store primary key values from the models you’ll be relating to. For most models, this means a PositiveIntegerField<\/a>. The usual name for this field is object_id.<\/li>
- Give your model a GenericForeignKey<\/a>, and pass it the names of the two fields described above. If these fields are named content_type and object_id, you can omit this \u2013 those are the default field names GenericForeignKey<\/a> will look for.<\/li><\/ol>\n\n\n\n