Ryan, After reading some of the other replies, and knowing how hard it can be to convince a developer, I wonder if perhaps showing them the result of an an extended SQL trace might help? Set up an extended trace, run a DML with 'update all columns' and one of update selected columns. TKPROF the output, maybe even do some 'walking the clock' analysis of the raw trace. Ed Stevens -----Original Message----- From: ryan_gaffuri@xxxxxxxxxxx [mailto:ryan_gaffuri@xxxxxxxxxxx] Sent: Tuesday, September 28, 2004 10:37 AM To: oracle-l@xxxxxxxxxxxxx Subject: looking for doc with diagrams on redo and undo for java developers Object Oriented programming is all about reuse so our java guys made a universal update statement that updates all columns in a table, even unchanged columns. I know its bad, but its a major re-write to change this. I was digging through the otn docs and some books and everything that leads me to this requires a significant amount of reading. Multiple chapters etc... anyone know a short article that explains undo and redo along with diagrams and why its bad to update unchanged columns that is easy for a non-oracle person to follow? checked the concepts doc, but they would probably have to read 50-70 pages to get the basic idea. -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l