Changes between Version 231 and Version 232 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
Aug 11, 2008, 12:21:32 PM (16 years ago)
Author:
Brian Rosner
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v231 v232  
    11231123```response_change```.
    11241124
    1125 ```save_model``` was introduced in [8266], but has been renamed to
    1126 ```save_form``` due to the new behavior which is to return unsaved instances
    1127 as opposed to saved instances in both ```save_form``` and ```save_formset```.
    1128 
    11291125== Removed several more deprecated features for 1.0 ==
    11301126
     
    11541150
    11551151Lastly, any user that is maintaining an external database backend will need to update their code to use the new interface. The new class-based approach should make backend development much easier, as common behavior can be inherited from the base classes in django.db.backends; only database-specific behavior should require implementation.
     1152
Back to Top