id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
14989	Allow serializers to non ovewrite fixtures objects if they are marked as non overridable	Manuel Saelices	nobody	"Look at this use case:

1. The developer creates a new Django project (i.e. with south support).
2. The developer creates the database schema and load the initial data (including in example a demo home page).
3. The manager modify home page, and other contents.
4. The webmaster upgrade the project, and executing ``migrate`` command (because south support).
5. With default Django serializers, all manager changes that exists as fixtures data will be lost.

I know [http://docs.djangoproject.com/en/1.2/howto/initial-data/#automatically-loading-initial-data-fixtures Django docs prevent about that], but It was wonderful you may mark objects as no rewritable, like this:
{{{
!xml
<?xml version=""1.0"" encoding=""utf-8""?>
<django-objects version=""1.0"">
  <object pk=""1"" model=""fooapp.foomodel"" overwrite=""no"">
    <field type=""SlugField"" name=""slug"">welcome</field>
    ...
  </object>
</django-objects>
}}}

Look at [https://dev.merengueproject.org/changeset/2851 this implementation] as implementation reference."		new	Core (Serialization)	dev					Unreviewed	0	0	0	0	0	0