Re: Impossible Database Design?
From: mAsterdam <mAsterdam_at_vrijdag.org>
Date: Wed, 17 May 2006 08:13:26 +0200
Message-ID: <446abe33$0$31650$e4fe514c_at_news.xs4all.nl>
>
>
> Seconded. Why not state a more realistic requirement, such as:
> support events up to 1000 years in the future? 1000 is much,
> much less than infinite, and so has the advantage of being actually
> possible.
>
> Also remember Scott McNealy's comment: "Most software
> has the shelf life of a banana." Your software probably won't
> still be in use in even 10 years.
Date: Wed, 17 May 2006 08:13:26 +0200
Message-ID: <446abe33$0$31650$e4fe514c_at_news.xs4all.nl>
Marshall wrote:
> Bob Badour wrote:
>
>>>It would be quite simple to write a calendar supporting true infinite >>>events by just leaving the end date empty but as far as I can think of >>>it won't be possible anymore to calculate overlaping events.. >> >>You have not been listening. Unless you have an infinite computer, you >>cannot create an infinite calendar.
>
>
> Seconded. Why not state a more realistic requirement, such as:
> support events up to 1000 years in the future? 1000 is much,
> much less than infinite, and so has the advantage of being actually
> possible.
>
> Also remember Scott McNealy's comment: "Most software
> has the shelf life of a banana." Your software probably won't
> still be in use in even 10 years.
Also remember that knowing that people actually built software with that assumption led to the millennium paranoia.
Arbitrary limits where none are logically necessary have quite a track-record (640Kb anyone?). Received on Wed May 17 2006 - 08:13:26 CEST