Re: On Indexes and Commits

General principle. when you insert a row into a table, you insert the index entries at the same time. There are minor variations on a theme, but as each INSERT statement
completes, the table and its indexes are self-consistent.

Rolling back is very expensive - start
looking into TEMPORARY TABLES
with 'on commit delete rows'.

--
Jonathan Lewis

Seminars on getting the best out of Oracle
Last few places available for Sept 10th/11th
See http://www.jlcomp.demon.co.uk/seminar.html




Kirt Thomas wrote in message ...


>We're sitting here puzzling over this :)

>

>Our developers use a table to store data during the execution of a

>report, they may end up inserting several to tens of thousands of

>records into this table to be reported on (of course this is a bad,

>but that's neither here nor there right now).  The way the dev's are

>handling the records in this 'temp' table is to do no commit, and

>issue a rollback after the report is done - effectively cancelling the

>inserts.  This allows multiple reports to run at the same time as each

>report only see's it's own sessions data.

>

>My assertion is that doing things this effectively negates any indexes

>on the table.  I don't see how they could be used w/out commiting the

>data.  Is this true?  Thanks.