2009/1/23 Ned Batchelder <n...@nedbatchelder.com> > 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. >
Where can I find something about the limits of mysql or postgresql? If I have 50 plants and ~8000 tuple for every plant every day, and a dimension of 30 fields (double), i have 400kb for every plant /day. In a year I will reach 8GB of data. I will have 2 tables for a total of 60 fields, + indexes and other django fields. Is that reasonable to be handled in a single table? -- Alessandro Ronchi Skype: aronchi http://www.alessandroronchi.net SOASI Soc.Coop. - 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 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
