It's funny. Everyone I ask about this problem says to use the other type of Field (either OneToOne or ForeignKey). I have tried both. See this thread for my problems with OneToOne: http://groups.google.com/group/django-users/browse_thread/thread/9789d5e4bf24a4c3/
I just recently upgraded from 0.95 to 0.96-pre and this seems to have solved the problem of saving an edit_inline ForeignKey in the admin. Also, I am writing custom manipulators and views instead of using the generic views, so this problem is avoided. It's a shame the generic views can't handle my model relationships, but it's probably good practice for me to write custom manipulators/views anyway. I'm using a Manipulator class (from the code wiki, can't find the link at the moment) that is really simplifying things. (That is, unless manipulators completely go away and I have to re-write them all in some futuristic way.) So I guess this problem is solved. Thanks, Grant --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
