On Thu, Aug 6, 2009 at 12:38 AM, Wojciech Gryc<wojci...@gmail.com> wrote: > > Thanks for your replies! > > The problem with storing the user ID for each table and then filtering > by the ID is that once the data set grows very large, this will become > extremely slow (as far as I understand). > > I expected to have about 2000 pieces of information per user, with > several dozen users (at least). Filtering by user ID each time would > be extremely wasteful, would it not?
I think it really depends on database - however such a simple operation like filtering based on indexed field shouldn't take much resources . How about database views? Several dozens of users means several dozens * number of content types tables... --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
