Vizcayno wrote: > but the only idea > that this recommended solution represents a double processing > (accommodate the list) and double use of memory with 'table' restrained > me to continue and send this message
'Premature optimization is the root of all evil' :-). In this case, if only your data is not sized in gigabytes, I am pretty sure that cost of this processing would be absolutely invisible both in speed and memory. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
