Thanks, everyone, for your replies! Doing a reply-to-all thing here... On Sep 10, 9:27 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote: > This has come up a number of times over the years, and I still haven't > wrapped my head around why somebody would need this functionality... > Surely one could just use the "standard" admin for the third-level > objects, then use two-level inlines for the first- and second-level > objects?
It's not so much as a "need" as a "nice to have". I currently do what I think you describe, given A has many Bs has many Cs -- class A has class B as an inline, and when I am done with those two, I navigate to the admin section for class C, select the class B I just created in the ForeignKey dropdown, and create that third object. This obviously works, but it gets pretty tedious when doing lots of data entry, especially when I have multiple B/C groupings per instance of A. Although, now that I think on it, perhaps I have it backwards, and you're saying to use a regular no-inlines form for class A, then do a series of save-and-edit-new for a B+C edit-inline relationship? That would actually make a bit more sense... On Sep 10, 7:19 pm, "Joseph Kocherhans" <[EMAIL PROTECTED]> wrote: > It turns out that recursive inlines are hard. [...] Thanks, I was expecting someone had taken a stab at it, but hadn't run across any mentions. > That said, I'm pretty stupid, and the fact that I couldn't figure > something out doesn't mean a whole lot. My suggestion to anyone who > wants to try this is to completely start over. Don't use the FormSet > code. It probably won't help you. Also, maybe take a look at > FormEncode. If I remember correctly, it can do such things. And here I thought *I* was modest :) Thanks for this also, advice noted. > I'd wager that none of the core devs are going to spend any time > implementing it Oh, certainly! That was never my intent; I'd hate to be That Guy standing up and going "please implement feature X for me, I need it right now, chop chop!". Just wanted to get a sense of whether I was on the right track or totally out in left field. On Sep 10, 7:38 pm, "Justin Fagnani" <[EMAIL PROTECTED]> wrote: > I'm currently working on recursive inline editing using formsets, but > not in the admin. [...] my patch > for that is in #8160. Thanks for the note, and good luck! Ironic that you're taking this approach given Joseph's advice above, but you sound like you're making progress -- I'll check out your patch. On Sep 10, 6:52 pm, Cortland Klein <[EMAIL PROTECTED]> wrote: > Since I couldn't find an existing ticket for nested or recursive > inlines in admin, I filed #9025. And thanks for opening that ticket; although given what Joseph said above, I'm not sure if it will stay open, or if it would be considered a partial duplicate of Justin's #8160. I can't write a short email, can I? :) Thanks again, all, for the discussion. For now I think I may try re-jiggering my existing edit- inline setup and see if that helps my data entry speed, and I'll definitely watch #8160/#9025 with interest -- I think this is still a noble goal. May pitch in as well if I have time, of course. Regards, Jeff --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
