RE: data modelling question - job vs. job history table

> -----Original Message-----
> Mercadante, Thomas F
>
> Why make it sooo complicated? I like the third table -
> Job_History that
> shows what job ran and when. Much clearer now, and in a year
> from now when
> you (or someone else) goes and reviews what you did.

Because I can? Because when I make something complicated people think I'm smart? :)

My first idea was to have a job_history table, but when I was looking at my tables I noticed that the job_schedule table and the job_history table had pretty much identical columns, and I said to myself "why have two tables when all the columns are the same?"

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Jacques Kilchoer
  INET: Jacques.Kilchoer_at_quest.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).