Merci beaucoup Monsieur. I agree with your point in the second paragraph.
> -----Original Message-----
> Stephane Faroult
>
> My personal preference is with solution 2 - moving the
> current information to JOB. The scheduler can quietly insert
> into JOB_HISTORY when it is done with a job, and update the
> current line (do it through triggers if you like). Solution 3
> violates the beloved KISS principle ...
> Moreover, when you want to do some maintenance operation over
> the history table (purge, archival, whatever) you are going
> to interfere with the process which presumably polls the table.
>
> My EUR 0.02
--
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).
Received on Thu Nov 13 2003 - 14:34:26 CST
