Re: How to handle secondary keys in partitioning?
That's great news.
> "allow pruning on INSERT/UPDATE/DELETE."
Does that mean currently no pruning is done for INSERT/UPDATE/DELETE?
So if I insert a new record, the SQL statement is run for all partitions? But how is that possible since the new record can only be inserted into one partition?
And what about UPDATE/DELETE - are those statements run on all partitions without pruning?
So if I have N partitions, an INSERT/UPDATE/DELETE statement would be run N times sequentially, once on each partition?
Subject
Views
Written By
Posted
4383
May 04, 2010 12:46AM
2453
May 04, 2010 01:29PM
2087
May 04, 2010 04:30PM
2305
May 05, 2010 02:20AM
2152
May 06, 2010 12:04AM
2556
May 06, 2010 03:23PM
2196
May 06, 2010 10:50PM
2163
May 07, 2010 02:38AM
2118
May 08, 2010 05:31PM
2178
May 09, 2010 04:37AM
Re: How to handle secondary keys in partitioning?
2063
May 09, 2010 12:41PM
2052
May 09, 2010 01:23PM
2143
May 12, 2010 05:29AM
2575
May 06, 2010 12:34AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.