Re: Impossible Database Design?

From: Nikolai Onken <nikolai.onken_at_gmail.com>
Date: 17 May 2006 01:06:26 -0700
Message-ID: <1147853186.164597.278500@i40g2000cwc.googlegroups.com>

> Not really.

Hmm, so probably then I should go for every event gets stored as a single entry in the db...

> Because an infinite calendar would require infinite memory to represent
> the largest date.

I prefer to tell a client though that "something doesn't work because computers can't yet handle it" rather than "we have to reprogramm because the concept was not proof when developed" (I know that it is really irrelevant since my client won't go ask me in 243678 why something doesn't work but I am just curious to what the best solution is)

Would you argue that the calendar example I gave is not a working infinite calendar (with some constraints, querying into the future is only possible on a defined scale)? It still would work like a charm in 2432654376 :) Received on Wed May 17 2006 - 03:06:26 CDT