Looks like a general refactoring of admin queryset handling is needed. That would also cater for this use case (InlineAdmin objects supporting queryset() would solve your case).
See http://code.djangoproject.com/ticket/11019 and http://code.djangoproject.com/ticket/10761 . On May 22, 10:24 am, Eric Abrahamsen <gir...@gmail.com> wrote: > I've got a Model A with a foreignkey to Model B, which is limited to > certain instances of Model B using limit_choices_to in the foreign > key. If I set up the admin so that Model A instances are editable > inline through Model B instances, all Model B instance change forms > get forms for Model A inlines, even those that should be excluded > according to the limit_choices_to. These Model A inlines can be saved > to Model B instances, even when they shouldn't. > > I'd like to open a ticket for this and look into providing a patch > unless > > 1. this is a case of "just make your own admin functionality" > 2. it's otherwise hard or messy or undesirable. > > Does this seem like an acceptable idea? > > Eric --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
