This was my best solution. I honestly wouldnt ever encourage anything where you dont specify which foreignkeys to follow. JOINs can get very slow when they expand beyond 2 or 3 tables, especially when table sizes increase.
On Aug 2, 2:28 am, Michael Radziej <[EMAIL PROTECTED]> wrote: > On Thu, Aug 02, David Cramer wrote: > > > Seems I slipped in the diff. I have to actually apply the patch to at > > least 2 different versions of Django with our current setup, can get > > tedious :P > > > *args should be *fields :) > > ;-) > > Well, for the deeper levels, is there a way to express "follow > myforeignkey__user recursively" and also "follow myforeignkey__user, but no > deeper" without using the depth parameter (because you might want to follow > to different depths in different foreign keys)? > > Michael > > -- > noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg - > Tel +49-911-9352-0 - Fax +49-911-9352-100http://www.noris.de- The > IT-Outsourcing Company > > Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel, Hansjochen Klenk - > Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689 --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
