On Wed, Oct 29, 2008 at 4:35 PM, AndrewD <[EMAIL PROTECTED]> wrote:
>
> # models.py
> class Membership(models.Model):
> person = models.ForeignKey(Person)
> group = models.ForeignKey(Group)
>
> # admin.py
> class MembershipInline(admin.TabularInline):
> model = Membership
> raw_id_fields = ('person',)
> extra = 1
>
> class PersonAdmin(admin.ModelAdmin):
> # ... add other features
> inlines = (MembershipInline,)
> admin.site.register(Person, PersonAdmin)
The MembershipInline doesn't make much sense. You have put the foreign
key used for the relationship between Membership and Person in a
raw_id_field. In this case it would normally be implied by the
relationship you have setup. Is explicitly putting 'person' in
raw_id_fields intentional, it should rather be 'group' if anything.
> The resulting admin tool generates a separate Membership ID field
> (table row) with a spyglass next to it. Each spyglass sets or replaces
> the single ID in that row.
I presume you are asking a question here? That extra row is
technically a bug in the fact that it should always render it hidden.
--
Brian Rosner
http://oebfare.com
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
