Changes between Version 175 and Version 176 of BackwardsIncompatibleChanges

Timestamp:

Jul 1, 2008, 10:11:36 AM (16 years ago)

Author:

Jacob

Comment:

Added details about [7814]

BackwardsIncompatibleChanges

@@ -61 +61 @@
  * [7799] June 30, 2008 [#BooleanFieldsinnewformsenforcerequired BooleanFields in newforms enforce "required"]
  * [7806] June 30, 2008 [#DefaultUserorderingremoved Default User ordering removed]
+ * [7814] July 1, 2008 [#Uploadedfilechanges Uploaded file changes]
 
 == Database constraint names changed ==
@@ -347 +348 @@
 >>> management.call_command('loaddata', 'test_data', verbosity=0)
 }}}
+
 
 
@@ -647 +649 @@
 
 Note that the admin interface will still behave the same as prior to this change, since it automatically orders the users by their name, just as before. So no change will be noticable there.
+
+== Uploaded file changes ==
+
+[7814] introduced changes to the way Django handles uploadded files. Most of the changes are in the form of added flexibility and performance (for details, see the [http://www.djangoproject.com/documentation/upload_handing/ upload handling documentation]).
+
+However, as part of the change, the representation of uploaded files has changed. Previous, uploadded files -- that is, entries in {{{request.FILES}}} -- were represented by simple dictionaries with a few well-known keys. Uploaded files are now represented by an [http://www.djangoproject.com/documentation/upload_handing/#uploaded-file-objects UploadedFile object], and thus the file's information is accessible through object attributes. Thus, given {{{f = request.FILES['some_field_name']}}}:
+
+|| '''Old'''                            || '''New'''                    ||
+|| {{{f['content']}}}           || {{{f.read()}}}               ||
+|| {{{f['filename']}}}          || {{{f.file_name}}}    ||
+|| {{{f['content-type']}}}      || {{{f.content_type}}} ||
+
+The old dictionary-style key access is still supported, but will raise a {{{DeprecationWarning}}}.