On Aug 5, 11:38 pm, 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? > > Thanks, > Wojciech
No, not at all. This is what databases are *designed* to do, and they do it super-efficiently. 2000 rows per user * dozens of users is absolutely nothing - there are dbs with many millions of rows out there. This is absolutely the right solution. -- DR. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
