Changes between Version 13 and Version 14 of AppEngine


Ignore:
Timestamp:
02/25/2009 06:47:46 AM (6 years ago)
Author:
wkornewald
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AppEngine

    v13 v14  
    1111== Summary ==
    1212
    13 The most important changes at the Django level are:
    14  * support for setting an owner model for !ManyToManyFields (i.e., there is no intermediary table and the field's data could be stored on either the model defining the relation or on the other model) and !ModelForm should handle that case efficiently (i.e., try to save the relations together with the model instead of afterwards in save_m2m)
    15  * support for !ListField (stores a list of values of a certain type; DB backends could use this internally for !ManyToManyFields without an intermediary table) and [http://code.djangoproject.com/ticket/2417 BinaryField]
    16  * support for batch save() and delete()
    17  * support for email backends
    18  * support for running Django from a zip package
     13At the Django level we need support for:
     14 * setting an owner model for !ManyToManyFields (i.e., there is no intermediary table and the field's data could be stored on either the model defining the relation or on the other model) and !ModelForm should handle that case efficiently (i.e., try to save the relations together with the model instead of afterwards in save_m2m)
     15 * !ListField (stores a list of values of a certain type; DB backends could use this internally for !ManyToManyFields without an intermediary table) and [http://code.djangoproject.com/ticket/2417 BinaryField]
     16 * batch save() and delete()
     17 * email backends
     18 * running Django from a zip package
    1919
    2020== Reminder: Datastore and request limitations ==
     
    129129== File uploads ==
    130130
    131 The file upload handling code should never assume that it has access to the file system. Instead, it should assume that the file gets uploaded directly into the datastore or indirectly (e.g., via POST to S3 and then Django just gets notified when the upload is finished). This means that imports of file system functions should be deferred as much as possible.
     131The file upload handling code should never assume that it has access to the file system. Instead, it should be supported that the file gets uploaded indirectly into the datastore (e.g., via POST to S3 and then Django just gets notified when the upload is finished). This means that imports of file system functions should be deferred as much as possible.
    132132
    133133== Permissions and content types ==
Back to Top