Re: Impossible Database Design?

Nikolai Onken wrote:

> Hey Volker,
>
> thank you for your reply!! Thats what I was wondering! How long could
> Outlook actually run..
> I think the best solution for my case would be to have three tables:
>
> events:
>
> datetime_start
> datetime_end
> name
> description
> other_fields
>
> event_exceptions:
>
> datetime_start
> datetime_end
> replacingperiod_datetime_start
> replacingperiod_datetime_end
> name
> description
> other_fields
>
> event_rules:
>
> datetime_start
> datetime_end (if NULL = never ending)
> repeat_pattern
> name
> description
> other_fields
>
> Then I write the data into the events table according to repeat_pattern
> and event_exceptions...
> This at the same time will enable me to run queries on future events
> and have some sort of support for infinite repeating events.
> Would anyone concider this a workable design for a calendar?

Whether it is a workable design will be a direct consequence of the full set of requirements -- the vast majority of which you have omitted. Anyone who gives detailed or emphatic opinions on the merits of the design above is a crank. Received on Wed May 17 2006 - 17:03:15 CEST