Nope. Did it again on a clean project with the same models migrated then by South.
Same error. Any other clues? Thanks for replies. On Dec 12, 3:25 am, Shawn Milochik <[email protected]> wrote: > Why did you manually add a 'slug' field to your database after modifying the > model? Django's syncdb does a lot more than just create the field; depending > on which database you're using, it does a few other things and overrides some > defaults. I wonder if there's a disconnect there. If this project is > currently in production and you can't re-run syncdb, then I highly recommend > South (south.aeracode.org) for database migrations. > > I suspect that the problem is because the field was added manually. Try > adding the field with South. It takes care of the nitty gritty details for > you. > > Worst-case, make a copy of the model in question with a different name. Then > try to create new instances of it from your external script. If that works > (after adding that new model to the database with syncdb), then it's almost > definitely due to the way the model and database were modified after-the-fact > manually. > > Shawn -- 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.
