You don't need to create new tables like this. These database systems are very good at handling large amounts of data. Add a field plant to your model, make sure it is indexed, and use it to query for the data you want. The entire system from the database up through the ORM and the rest of Django has been built to do a good job with this model. Trying to create new tables as you propose is going against the grain at every level.
--Ned. http://nedbatchelder.com Alessandro Ronchi wrote: > I need to start a project with thousand of tuples every day for N > solar plants. > *I think I need multiple databse tables for a single model,* because I > can divide every plant's tuples. > So I need something to create a (#1 table) GenericPlantModel and (#n > tables) GenericPlantData and when I create a new GenericPlantModel > Instance I need to create a new GenericPlantData_1 table instead using > the same GenericPlant one (with millions of tuples). > > Is it possible? > What's the limit of the number of tuples I can handle without problems > in MySQL or PostgreSQL (and witch one is the best, for this heavy work)? > > -- > Alessandro Ronchi > Skype: aronchi > http://www.alessandroronchi.net > > SOASI Soc.Coop. - www.soasi.com <http://www.soasi.com> > Sviluppo Software e Sistemi Open Source > Sede: Via Poggiali 2/bis, 47100 Forlì (FC) > Tel.: +39 0543 798985 - Fax: +39 0543 579928 > > Rispetta l'ambiente: se non ti è necessario, non stampare questa mail > > > -- 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
