I’m going to make a Mysql based calendar system where you can have repeating pattern for lets say every monday forever and ever. It must also cover static/once-only events. What I’m wondering about, is which solution would be most logical (and best) for me to use. I have four methods which I’m wondering to chose between.
Make a function which accepts parameters
to. This function would create a temporary table table which imports existing static schedule through
INSERT ... SELECT. Afterward it would read of the pattern table and populate the temporary table through the peroid based on
This solution seems nice from the point of view that queries will be simplier to fetch data with and it works into infinity since you can just repopulate the table depending of which month you’re loading. What I’m curious about is whenever this might be a laggy way to do it or not.
Create and join given patterns through a subquery and
JOIN with static calendar.
This seems to be rather annoying since the queries would be a lot more bigger and would probably not be good at all(?).
INSERT pattern for lets say one year ahead. Then I guess a cron job would repopulate to make it one year ahead always.
This is a simple way to do it, but it feels like a lot of unneeded data stored and it doesn’t really give the infinity which I’m after.
Method #4 (Suggested by Veger)
If I understand correctly, this method would fetch the pattern from another query and creates events upon execution. It’s similar to my thoughts regarding Method #1 in that way that I consider simple pattern to create several rows.
However if this would be implemented outside Mysql, I would loose some database functionality which I’m after.
I hope you guys understood my situation, and if you could suggest either given and argue why it’s the best or give another solution.
Personally I like the Method #1 the most, but I’m curious if it’s laggy to repopulate the calendar table each and every call.
I have built this kind of calendar before. I found the best way to do it is to approach it the way that crons are scheduled. So in the database, make a field for minute, hour, day of month, month, and day of week.
For an event every Friday in June and August at 10:00pm your entry would look like
Minute Hour DayOfMonth Month DayOfWeek 0 22 * 6,8 5
You could then have a field that flags it as a one time event which will ignore this information and just use the start date and duration. For events that repeat that end eventually (say every weekend for 3 months) you just need to add an end date field.
This will allow you to select it back easily and reduce the amount of data that needs to be stored. It simplifies your queries as well.
I don’t think there is a need to create temporary tables. To select back the relevant events you would select them by the calendar view. If your calendar view is by the month, your select would look something like:
SELECT Events.* FROM Events WHERE (Month LIKE '%,'.$current_month.',%' OR Month = '*') AND DATE(StartDate) >= "'.date('Y-m-d', $firstDayOfCurrentMonth).'" AND DATE(EndDate) <= "'.date('Y-m-d', $lastDayOfCurrentMonth).'"
Obviously this should be in a prepared statement. It also assumes that you have a comma before and after the first and last value in the comma separated list of months (ie.
,2,4,6,). You could also create a
Month table and a join table between the two if you would like. The rest can be parsed out by php when rendering your calendar.
If you show a weekly view of your calendar you could select in this way:
SELECT Events.* FROM Events WHERE (DayOfMonth IN ('.implode(',', $days_this_week).','*') AND (Month LIKE '%,'.$current_month.',%' OR Month = '*')) AND DATE(StartDate) >= "'.date('Y-m-d', $firstDayOfCurrentMonth).'" AND DATE(EndDate) <= "'.date('Y-m-d', $lastDayOfCurrentMonth).'"
I haven’t tested those queries so there maybe some messed up brackets or something. But that would be the general idea.
So you could either run a select for each day that you are displaying or you could select back everything for the view (month, week, etc) and loop over the events for each day.
I like Veger’s solution best .. instead of populating multiple rows you can just populate the pattern. I suggest the
crontab format .. it works so well anyway.
You can query all patterns for a given customer when they load the calendar and fill in events based on the pattern. Unless you have like thousands of patterns for a single user this should not be all that slow. It should also be faster than storing a large number of row events for long periods. You will have to select all patterns at once and do some preprocessing but once again, how many patterns do you expect per user? Even 1000 or so should be pretty fast.
I’ve had this idea since I was still programming in GW Basic 😉 though, back then, I took option #3 and that was it. Looking back at it, and also some of the other responses, this would be my current solution.
start (datetime) stop (datetime, nullable) interval_unit ([hour, day, week, month, year?]) interval_every (1 = every <unit>, 2 every two <units>, etc.) type ([positive (default), negative]) - will explain later
type field determines how the event is treated:
- positive; normal treatment, it shows up in the calendar
- negative; this event cancels out another (e.g. every Monday but not on the 14th)
This query will narrow down the events to show:
SELECT * FROM `events` WHERE `start` >= :start AND (`stop` IS NULL OR `stop` < :stop)
Assuming you query a range by dates alone (no time component), the the value of
:stop should be one day ahead of your range.
Now for the various events you wish to handle.
start = '2012-06-15 09:00:00' stop = '2012-06-15 09:00:00' type = 'positive'
Event occurs once on 2012-06-15 at 9am
bounded repeating event
start = '2012-06-15 05:00:00' interval_unit = 'day' interval_every = 1 stop = '2012-06-22 05:00:00' type = 'positive'
Events occur every day at 5am, starting on 2012-06-15; last event is on the 22nd
unbounded repeating event
start = '2012-06-15 13:00:00' interval_unit = 'week' interval_every = 2 stop = null type = 'positive'
Events occur every two weeks at 1pm, starting on 2012-06-15
repeating event with exceptions
start = '2012-06-15 16:00:00' interval_unit = 'week' interval_every = 1 type = 'positive' stop = null start = '2012-06-22 16:00:00' type = 'negative' stop = '2012-06-22 16:00:00'
Events occur every week at 4pm, starting on 2012-06-22; but not on the 22nd
I would suggest something around the lines of this:
Split your Events table into 2 because there are clearly 2 different types recurring events and static events and depending on the type they will have different attributes.
Then for a given Event look-up you would run 2 queries, one against each Event Type. For the static events table you would defiantly need (at least) one datetime field so the lookup for a given month would simply use that feild in the conditions (where event_date > FirstDayOfTheMonth and event_date < LastDayOfTheMonth ). Same logic for a weekly/yearly view.
This result set would be combined with a second result set from the recurring events table. Possible attributes could be similar to crontab entries, using day of week/day of month as the 2 main variables. If you’re looking at a monthly view,
select * from recurring_events where DayOfWeek in (1,2,3,4,5,6,7) or (DayOfMonth > 0 and DayOfMonth < @NumberOfDaysInThisMonth )
Again similar if for a weekly/yearly view. To make this even simpler to interface, use stored procedures with all the logic for determining ‘which days of the week are found between date A and date B’.
Once you have both result sets, you could aggregate them together in the client then display them together. The adavantage to this is there will be no need for “mock/empty records” nor async cronjobs which pre-fill, the queries could easily happen on the fly and if performance actually degrades, add a caching layer, especially for a system of this nature a cache makes perfect sense.
I’m actually looking for something similar to this and my solution so far (on paper I didn’t start to structure or code yet) stores in 2 tables:
the “events” would get the date of the first occurrence, the title and description (plus the auto-increment ID).
the “events_recursion” table would cross reference to the previous table (with an event_id field for instance) and could work in 2 possible ways:
2.A: store all the occurrences by date (i.e. one entry for every occurrence so 4 if yo want to save “every friday of this month” or 12 for “the 1st of every month in 2012”)
2.B: or saving the interval (I would save it in seconds) from the date of the first event in a field + the date of the last occurrence (or end of recursion) in another field such as
INTERVAL: 604800 (a week if I’m not mistaken)
END: 1356912000 (should be the end of this year)
Then when you open the php that shows the schedule it would check for the event still active in that month with a joint between the two tables.
The reason why I would use 2 tables cross-referenced instead of saving all in one tables just comes from the facts that my projects sees very crazy events such as “every fridays AND the 3rd monday of every month” (that in this case would be 1 entry in the events tables and 2 with same “event_id” field in the second table. BTW my projects is for music teachers that here got small work on strict schedules decided 3 or 6 months at a time and are a real mess).
But as I have said i haven’t started yet so I’m looking forward to seeing your solution.
PS: please forgive (and forget) my english, first isn’t my language and second it is pretty late night and I’m sleepy
Maybe check out some great ideas from MySQL Events
the best solution depends on whether you want to favor standard compliance (RFC5545) or working exclusively within MySQL.
depend on on flexible your recurrence rule engine needs to be. If you want simple rules (every 1st of month or every January, …) then the solutions offered above have been detailed at length.
However should you want your application to offer compatibility with existing standards (RFC5545) which involves much more complex rules you should have a look at this SO post when building a calendar app, should i store dates or recurrence rules in my database?
I would do it as I explained here. It will create an infinite calander:
The downside is that there will be some calculation during the query. If you need a high performance website, preloading the data will be the way to go. You dont even have to preload all the events in the calendar, to make it possible for easy changing the values in a single event. But it would be wise to store all dates from now till ….
Now using cached values does make it less infinite, but it will increase speed.
Copy of awnser for easy access:
I would create a tally table with just one col called
id and fill that table with numbers from 0 to 500. Now we easily use that to make selections instead of using a while loop.
Id ------------------------------------- 0 1 2 etc...
Then i’d store the events in a table with
Name as varchar,
startdate as datetime and
repeats as int
Name | StartDate | Repeats ------------------------------------- Meeting | 2012-12-10 00:00:00 | 7 Lunch | 2012-12-10 00:00:00 | 1
Now we can use the tally table to select all dates between two dates by using:
SELECT DATE_ADD('2012-12-09 00:00:00',INTERVAL Id DAY) as showdate FROM `tally` WHERE (DATE_ADD('2012-12-09 00:00:00',INTERVAL Id DAY)<='2012-12-20 00:00:00') ORDER BY Id ASC ShowDate ------------------------------------- 2012-12-09 00:00:00 2012-12-10 00:00:00 2012-12-11 00:00:00 2012-12-12 00:00:00 2012-12-13 00:00:00 2012-12-14 00:00:00 2012-12-15 00:00:00 2012-12-16 00:00:00 2012-12-17 00:00:00 2012-12-18 00:00:00 2012-12-19 00:00:00 2012-12-20 00:00:00
Then we join this on the events table to calculate the difference between the startdate and the showdate. We devided the results of this by the
repeats column and if the remainder is
0, we have match.
All combined becomes:
SELECT E.Id, E.Name, E.StartDate, E.Repeats, A.ShowDate, DATEDIFF(E.StartDate, A.ShowDate) AS diff FROM events AS E, ( SELECT DATE_ADD('2012-12-09 00:00:00',INTERVAL Id DAY) as showdate FROM `tally` WHERE (DATE_ADD('2012-12-09 00:00:00',INTERVAL Id DAY)<='2012-12-20 00:00:00') ORDER BY Id ASC ) a WHERE MOD(DATEDIFF(E.StartDate, A.ShowDate), E.Repeats)=0 AND A.ShowDate>=E.StartDate
Which results in
Id | Name |StartDate | Repeats | ShowDate | diff --------------------------------------------------------------------------------- 1 | Meeting | 2012-12-10 00:00:00 | 7 | 2012-12-10 00:00:00 | 0 2 | Lunch | 2012-12-10 00:00:00 | 1 | 2012-12-10 00:00:00 | 0 2 | Lunch | 2012-12-10 00:00:00 | 1 | 2012-12-11 00:00:00 | -1 2 | Lunch | 2012-12-10 00:00:00 | 1 | 2012-12-12 00:00:00 | -2 2 | Lunch | 2012-12-10 00:00:00 | 1 | 2012-12-13 00:00:00 | -3 2 | Lunch | 2012-12-10 00:00:00 | 1 | 2012-12-14 00:00:00 | -4 2 | Lunch | 2012-12-10 00:00:00 | 1 | 2012-12-15 00:00:00 | -5 2 | Lunch | 2012-12-10 00:00:00 | 1 | 2012-12-16 00:00:00 | -6 1 | Meeting | 2012-12-10 00:00:00 | 7 | 2012-12-17 00:00:00 | -7 2 | Lunch | 2012-12-10 00:00:00 | 1 | 2012-12-17 00:00:00 | -7 2 | Lunch | 2012-12-10 00:00:00 | 1 | 2012-12-18 00:00:00 | -8 2 | Lunch | 2012-12-10 00:00:00 | 1 | 2012-12-19 00:00:00 | -9 2 | Lunch | 2012-12-10 00:00:00 | 1 | 2012-12-20 00:00:00 | -10
Now you could (and should!) speed things up. For instance by directly storing dates in a table so you can just select all dates directly instead of using a tally table with dateadd. Every thing you can cache and dont have to calculate again is good.