On 02/11/12 Tom Evans said: > Hmm, looks ok.. do you end up with two entries in the DB, one with the > old primary key, and one with the new primary key?
No, and I expected to. > Personally, I don't use natural primary keys with Django, I always let > it create an 'id' primary key, and then add a unique key to cover the > natural key, which avoids issues when you need to change the natural > key. The logic in ModelForm looks like this: I'm going to go that route, but this seems like a bug, so I'll report it. Mike -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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.
