Nope. Sorry for misdescription... Same error is "TypeError: 'slug' is an invalid keyword argument" when using: --- new_element = Element(title="title", date=datetime.now(), source=source_object, slug="slug") new_element.save() ---
And the same "_mysql_exceptions.Warning: Field 'slug' doesn't have a default value" when using: --- new_element = Element(title="title", date=datetime.now(), source=source_object) new_element.slug = "slug" new_element.save() --- The same errors from an outer script. From the shell or admin site - works still fine... On Dec 12, 5:56 pm, Shawn Milochik <sh...@milochik.com> wrote: > On Dec 12, 2009, at 8:08 AM, tezro wrote: > > > Nope. Did it again on a clean project with the same models migrated > > then by South. > > > Same error. Any other clues? > > > Thanks for replies. > > When you say "same error," do you mean this one: "Duplicate key name > 'news_element_slug'"? > > If so, then it appears that, despite the clean project, it's not a clean > database. Try using sqlite3 temporarily, or change the model name from News > to NewsTest or something. > > Shawn -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.