Re: calendar db-repeating event: insert or select?

In article <8oha69$9u6$1_at_nnrp1.deja.com>,   hkastler_at_my-deja.com wrote:
> Hi--
>
> I'm attempting to build a sql-server based calendar app. One of the
> requirements is to have a palm-pilot-like calendar feature where
 events
> can be repeated over days, weeks, months and years. Collecting the
> information is easy enough, but what is the best way to handle it? For
> each repeating event, should I insert a new record, or would it be
> better to do some computations on a table to come up with the correct
> records when called?
>
> I'm new to sql, so if my statements don't make sense, I apologize.
>
> Any help you could give is much appreciated. Thanks!
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>

The key question is whether the user might want or should be able to amend individual subsequent records. If NOT then a "view" joined to the additional dates might be a way of saving space. If YES then insert new records. The latter is more probable because of the probability that "the regular Wednesday meeting has been moved to Thursday next week" type of event.

Ken_hansen

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Fri Sep 01 2000 - 11:14:04 CEST