On Fri, 2009-01-09 at 05:33 -0800, klein.steph...@gmail.com wrote: [...] > This error is understandable because actually ClassA haven't > ForeignKey but the relation > between ClassA and ClassB is OneToOneField then ClassA know how to > access to his classb object. > > This behavior is one missing admin model feature or my aims is > inconsistent ?
It's just a case of things not intended to work that way. The inline editing feature works consistently in one direction for related models (foreign key and one-to-one are essentially the same for purposes here), not bidirectionally. Maybe you could knock up a patch to make this work and maybe it's worthwhile (I don't really have a strong opinion either way, beyond thinking that there's really no end to people twisting the admin interface beyond intended usage and perhaps the should re-evaluate their use-cases). This is "scratch your own itch" territory, I suspect. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
