Re: Grouping data by month

Shawn Milochik wrote:
> If this is something you're going to need a lot, I suggest adding a month field, then overriding the model's save() method to populate it from the date_time field. It would certainly save a lot of hassle, and could be a major performance boost.
>

I've seen these suggestions before but I don't think that suits my
application. There are millions of rows in my datum table and I'm
already minimising the row-level footprint so that tables and indexes
don't get too large. Besides, I don't need the month grouping a lot,
this use case is only about 20% of common usage.
> Alternatively, depending on what kind of data this is, perhaps you could use MongoDB via pymongo to write and recall this info. If it's just log data that's only written once and only read for reporting purposes, it might be easier and higher-performance, and you don't really need the power of the Django models.
>

It's measurement data, written only once but read many, many times for
analysis purposes. I took a brief look at MongoDB but I doubt it would
integrate well with the rest of my db for which I really need a real RDBMS.

Thanks for your suggestions though.

Has anybody else encountered this problem?

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.