Hey Gabor, On Thu, 2006-08-31 at 09:16 +0200, Gábor Farkas wrote: [...] > let's say you have a model called Owner, that references using a > foreignkey a Thing. > > ===================== > class Thing(Model): > name = CharField(maxlength=500) > ===================== > > > ===================== > class Owner(Model): > name = CharField(maxlength=500) > thing = ForeignKey(Thing) > ===================== > > now let's say you have a LOT of Things... like 50000. > > now, when you call Owner.AddManipulator(), he's going to fetch the WHOLE > Thing-table. just to construct the AddManipulator. > > (well, i REALLY hope that's not the case, but from the db-queries it > seems so)
It is so. It doesn't need to be: we could make it a lazy iterator, although that is not a 10 minute change (I tried it a few months ago when helping somebody on IRC and it took more than 10 minutes and still wasn't right and I've never gone back to fix it completely). Like a few other people noticing warts with manipulators, I've kind of been punting this hoping that the manipulator/form changes will make it go away or we can fix it in the new version (probably the latter). Since that now appears to be moving forwards, I'm going to stay the course there, since there are so many other things to do. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
