Hey Tony, >From my understanding of an Autonomous Transaction (which admittedly isn't much), the sync would always be one update behind, correct? Because the auto-trans would execute the sync in the trigger body, the current update/insert of the indexed column that caused the trigger to fire would not be committed at the time of sync. Or am I missing something here?
I glanced at the Catalog Index feature and methinks it deserves smore investigation. Thanks! Rich Jesse System/Database Administrator [EMAIL PROTECTED] Quad/Tech International, Sussex, WI USA -----Original Message----- Sent: Tuesday, November 13, 2001 17:00 To: Multiple recipients of list ORACLE-L I would suggest researching an Autonomous Transaction fired from the trigger to get around the commit executed by CTX_DDL.SYNC_INDEX. Another approach I would pursue is to evaluate the use of Catalog Indexes (8.1.7). If your requirements fit within the catalog index limitations (more like an Intermedia Text-lite) then you are in luck since they are transactional, hence no need for periodic synchronization. HTH Tony Aponte -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Jesse, Rich INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (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).
