Search Postgresql Archives

Re: Recurring events

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 6/06/2011 8:59, Thomas Guettler wrote:
Hi,

how do you store recurring events in a database?

Selecting all events in a week/month should be fast (comming from an index).

My solution looks like this:

Table event:

Columns: id, name, recurring, start_datetime, end_datetime

recurring is weekly, monthly, yearly or NULL.

end_datetime can be NULL (open end).

Can you create an indexed view with infinite rows? I only want to index
the last three year and the next three years.

An other solution would be to fill a table with "serialized" events. The recurring
events would be created and inserted into a table. This can only be done in a time frame
like above (last three year, next three years). If a recurring event gets altered,
all its serialized events need to be updated.

Any feedback?

I have had success using the instructions at

https://github.com/bakineggs/recurring_events_for


--
Troy Rasiah


--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux