Wow, I didn't even know those existed. Besides this bug, are these considered stable?
Are there plans to document them? I've got a data model that we may need to implement that could use just this feature. If we start playing around with them and see how they work I can try to help provide some docs. -Rob On Jan 25, 3:32 am, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > On 1/23/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > > > > > On 1/23/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > > > > I've just attached a unit test to the ticket. It seems to be the same > > > issue described in #2749 and #3081. I think I understand the problem; > > > the patch on #3081 is pretty much correct. I should have this sorted > > > out by tonight. > > > Ok - I've attached a patch with a fix to #3215. The fix is pretty much > > what is attached to #3081, cleaned up for a couple of edge cases. The > > patch fixes #3081, #3215 and #2749. > > > I haven't committed the fix - it's late, I'm jetlagged, and I'm not > > completely certain I haven't missed an edge case (in particular, the > > reverse case - the patch for #3081 contains protection in the > > reverse_m2m traversal, but as far as I can make out generic relations > > don't have a reverse representation).My jetlag has worn off, so now I can > > see the obvious problem that I > missed on Tuesday. I've checked in the fix as [4428]. > > Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
