>
> As I understand, and also as documented syncdb doesn't change existing
> table.


I wish that were true but its not the case. When I run syncdb, it will alter
the object if it was already created.

Here is what my initial_data.json file looks like:

[
    {
        "pk": 1,
        "model": "myapp.mymodel",
        "fields": {
            "title": "Foo"
        }
    }
]

When I first run this, it will create an object with the name "Foo". If I
change it in the admin to "Bar" and save it, then syncdb again, it changes
back to "Foo". Is there a way around this behavior? Is there something I can
put in my initial_data.json file to get it to work the way I want?

Thanks,
D

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to