> It looks impossible on the SQL side. I thought you coud join tables, > order by a field in authors table and then get results with DISTINCT to > eliminate duplication from joining. But it appears that DISTINCT > requires you to select fields that you order by which ensures that > duplication would stay. > > So the only way I see is to get everything on the client side and sort > in memory retreiving author list for each entry and making it a > string... Meaning that it would kill the DB right after first 10 users > will make their first 10 records.
I've been banging my head against some similar problems recently, mostly with legacy data that's poorly normalized. One optimization/hack that was suggested to me was adding a field that's only used for sorting (or selecting, as the case may be) -- like your hypothetical concatenated string -- and generating it at creation/update time with a pre-save hook. pb -- http://e-scribe.com/news/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
