Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> comp.databases.theory -> Re: Temporal database - no end date

Re: Temporal database - no end date

From: Marshall <marshall.spight_at_gmail.com>
Date: 20 Jan 2007 16:08:27 -0800
Message-ID: <1169338107.293008.46200@v45g2000cwv.googlegroups.com>


On Jan 19, 2:04 pm, "DBMS_Plumber" <paul_geoffrey_br..._at_yahoo.com> wrote:
> V.J. Kumar wrote:
> > Could you show with an example how the loss occurs ? You may be right,
> > but let's see.
>
> Suppose I have 5 things. 4 of them lasted for 1 'day' before they
> break.The other broke on the same 'day' it went out.
>
> What is the mean time to failure?
>
> Sum of 'time quanta' = 4.
> Number of things = 5.
>
> Mean time to failure = 0 time quanta.
>
> Pick any intuitive unit of 'time quanta', and you can construct an
> example where this problem arises.

This example only shows one thing: aliasing. Aliasing is well understood
for decades now. The way you avoid the problem above is to use higher resolution. Use milliseconds instead of days and this problem disappears.

In fact this is the exact same issue as any other use of digital signals to model continuous functions. If this were an actual impossibility as claimed, then digital audio would not work, and jpegs would look like gray goop. But of course the actual issue is being ridiculously overstated. Almost the entire world models the reals with floating point; almost the entire world models audio with digital data; and an ever increasing fraction of the world does the same with video. IEEE 754, MP3, HDTV, anyone?

Marshall Received on Sat Jan 20 2007 - 18:08:27 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US