RE: Rollback per transaction %:73 %?

Yep, merge should be used whenever you can. This should eliminate the issue I mentioned... I was talking more about implications of "insert->if failed then update" approach, should anyone still go with it.

--
Regards,
Tanel Poder
http://blog.tanelpoder.com <http://blog.tanelpoder.com/> 

 



  _____  

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
On Behalf Of Flado
Sent: Friday, August 08, 2008 21:16
To: oracle-l_at_freelists.org
Subject: RE: Rollback per transaction %:73 %?





*	From: Tanel Poder <tanel.poder.003_at_xxxxxxx> 




*	To: "'Wiktor Moskwa'" <wmoskwa_at_xxxxxxxxxxxx> 




*	Date: Fri, 08 Aug 2008 19:22:47 +0800 


Hi Wiktor,

In theory you should choose the approach based on which case occurs mostly -
if you are expecting 99% of inserts to fail as corresponding rows already
exist in database (and need to be updated instead) then better start with


update and if 0 rows found then insert. And vice versa, if you expect to
insert 99% of rows and only update 1% then better start with insert (and if
it fails then update).

-- In theory, you sould choose MERGE in such cases, no?



--
http://www.freelists.org/webpage/oracle-l