Oracle if inserting or updating
I told him he should retract it all right away and then republish it later as series of articles that debunk many of the "myths" from the tuning books out there. He has choosen to not take that path, although he did say he would rewrite and post a corrected version in 3 or 4 days but that was 5 days ago.so for now, pretend that series of articles doesn't exist.
I completly agree with you, even i' ve compares each other. Please i would like what you think about the author suggestion regarding commit.What do you propose on a large transaction running out of rollback segment space ?It seems like the only way around is to have some level of commit frequency ? August 15, 2002 - pm UTC Nope, I feel (strongly) that your rollback segments should be sized for all of your day to day transactions. If you have a large transaction (keyword = transaction) then by definition you cannot commit.It'll be more cost effective then writing the one time procedural code that needs to be restartable (for WHEN it fails) and not update the same row twice (which typically corrupts the data). GROUP BY and Predicate Clauses" completely misses the point of the HAVING clause, and is trivial. Just fyi, the author emailed me asking for comments -- I commented on 1-26 and sent him my feedback point by point. (49 is a copy of 14 btw more or less) August 21, 2002 - pm UTC Here is the bottom line: ignore all the points in that article as it exists now.I was a little "harsh", eg: straight forward, perhaps in my review directly to him and do not feel like cleaning it up for posting here.
Search for oracle if inserting or updating:
It is not any harder for us to manage 15 gigawads or 15 bytes of undo.