Re: Is this a good use for an IOT type table or are there better solutions.

> we have a table with following structure
>
> ID NUMBER NOT NULL,
> DATESTAMP DATE NOT NULL,
> HOUR NUMBER NOT NULL,
> AAMP NUMBER,
> BAMP NUMBER,
> CAMP NUMBER,
> CAT NUMBER
>
> it has a unique index on ID, DATESTAMP, HOUR. it is used for access and
> aslo enforces uniqueness

Silly question, but why is there a column called HOUR when there is a DATE column as well? The DATE column will hold the date and the time, including the hour. IS the HOUR column redudant or is there another use?

Cheers,
Brian

-- 
===================================================================

Brian Peasland
dba_at_remove_spam.peasland.com

Remove the "remove_spam." from the email address to email me.


"I can give it to you cheap, quick, and good. Now pick two out of
 the three"