When we upgraded to Django 1.7 and Django Rest Framework 3.0, I didn't push the corresponding fixes for those upgrades (see issue #11). The following are the most important changes:
Upgrade your packages to Django 1.7.5 and DRF 3.0.
Remove south from your installed packages and from INSTALLED_APPS in your settings.py.
Use Django to make and run migrations (i.e. to update the models and database). For more information on that, please see Django's how-to.
In short though, please do not use the manage.py syncdb command anymore and get used to migrate and makemigrations.
:sparkling_heart: The Django and DRF upgrade finally addressed some major pain points I was having with model relationships and nesting. :sparkling_heart: No one but me cares about that currently, but it is going to be so great. What you should care about is that:
.object has been replaced with .validated_data when using serializers
ModelSerializers need to define a custom create() function instead of using the default. The default create() packaged in ModelSerializers is the replacement for .object previously returning a populated Model object, but the default method calls .create() followed by save() which is very bad. :boom:
When we upgraded to Django 1.7 and Django Rest Framework 3.0, I didn't push the corresponding fixes for those upgrades (see issue #11). The following are the most important changes:
INSTALLED_APPS
in your settings.py.manage.py syncdb
command anymore and get used tomigrate
andmakemigrations
..object
has been replaced with.validated_data
when using serializersModelSerializers
need to define a custom create() function instead of using the default. The defaultcreate()
packaged inModelSerializers
is the replacement for.object
previously returning a populated Model object, but the default method calls.create()
followed bysave()
which is very bad. :boom: