Nick, if all of your dynamically-created tables in fact have the same schema (set of columns), then you definitely should make one table for all your users to share. Be sure to index the columns that will be used in your WHERE clauses, and your table will perform fine.
--Ned. Malcolm Tredinnick wrote: > On Sun, 2007-07-15 at 23:37 +0800, nick feng wrote: > >> Hi Ned, >> >> Thanks for your reply. >> First, your question is my doubt. >> And my problem is, if I did the same thing as you said, I will create >> a table contains a great deal of data in it, this may cause the >> "select" operation very slow, the users may feel it hard to suffer >> from.... >> > > Database tables can contain millions and millions of rows and they will > still perform quickly. You are trying to do something that is very > fragile to avoid doing something that databases are designed to handle. > Don't optimise prematurely. > > Regards, > Malcolm > > > -- Ned Batchelder, http://nedbatchelder.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
