On Fri, Jan 8, 2010 at 9:36 PM, tom <toab...@googlemail.com> wrote: > Hi, > > i use postgres and want to use partitioning for tables (see > http://www.postgresql.org/docs/8.3/interactive/ddl-partitioning.html ) > > My Model looks like this: > > class Measurand(models.Model): > project = models.ForeignKey(Project) > avg_value = models.DecimalField(max_digits=10, decimal_places=4, > db_index=True) > > > I never want to query over all measurands. I just want to query over > all measurands from _one_ project like this: project.measurand_set.all > () > > So the best solution i think is to have one table for every project. > Is this possible with django and the new multidb-api?
The short answer is that you're on your own here. Regardless of how nice and helpful they might be, Django doesn't provide explicit support for the features of specific databases. I'm not sure that multi-db will help you out here - you don't need different connections to the database, you need different tables in a single database. Your one-table-per-project approach sounds a little closer to the mark, but there are plenty of details that will need to be worked out (especially with regards to writing initial SQL scripts to set up triggers and the like). So - good luck, but you're in uncharted territory. Yours, Russ Magee %-)
-- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
