What are the normal design patterns for a thing like this -- populate a database with multiple dates when a recurring event is added?
Well, the way I would do it, is to calculate when the next event will occur, and then schedule that. When that event is triggered, you can calculate the next occurrence. So there is never a need to store more than one date.
As for the exceptions list... You can use cron as the base, but instead of a command line, you store a symbolic name... or an ID. Specify the associated command line separately. You can have more entries for one name, and give each a precedence, pretty much just like the filter rules for an email/usenet client. Specify what you want to happen: run, or suppress. The first rule that triggers specifies what will happen at that specified time. And when the verdict is to suppress, you'll have to calculate the next occurrence after that time...
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|