Re: Impossible Database Design?

From: Nikolai Onken <nikolai.onken_at_gmail.com>
Date: 17 May 2006 07:31:35 -0700
Message-ID: <1147876295.833122.31520@i39g2000cwa.googlegroups.com>

> Apparently, you lack comprehension of the terms 'finite' and 'infinite'.
> I suggest you ponder the difference between them and re-read what I
> already posted.

No I don't think so, there are only different ways to represent finity and infinity in a database - its not about 64bit, or capacity or computer power (it is when starting to calculate with the data but that abviously isn't such a big deal since calendars usually don't need to calculate more than say 3 years in advance).

It seems that If I go for the way where I set the date_end to NULL when having infinite events then I compromise ability to calculate for example overlapping events appearing in the infinite future (though i could calculate overlaps in a timewindow). Or I store events as single entries in a db, so I compromise 'infinity' but can calculate overlapping events in the future... Funny, so both solutions are the same ? :)
Anyways - I don't want to tire you guys and really apprechiate your replies... Is this such a common problem? I can't find so many sites discussing this issues though there are lots of calendar applications...
Regards,

Nikolai Received on Wed May 17 2006 - 09:31:35 CDT