Comments on: PL/SQL http://itknowledgeexchange.techtarget.com/itanswers/plsql/ Tue, 21 May 2013 11:54:54 +0000 hourly 1 By: inprise http://itknowledgeexchange.techtarget.com/itanswers/plsql/#comment-60170 inprise Fri, 20 Feb 2009 10:12:23 +0000 #comment-60170 yes it s the problem,where clause causing the problem.i am looking into my code.

]]> By: sivu http://itknowledgeexchange.techtarget.com/itanswers/plsql/#comment-60165 sivu Fri, 20 Feb 2009 07:12:47 +0000 #comment-60165 Yes!! what carlos saying is perfect can you send check the Where Clause criteria. Are you finding any rows with this condition??

]]> By: carlosdl http://itknowledgeexchange.techtarget.com/itanswers/plsql/#comment-60085 carlosdl Wed, 18 Feb 2009 20:56:32 +0000 #comment-60085 Inserts don’t include a condition. Anytime you execute an insert, the desired row will be inserted unless an error occurs, on the other hand updates will affect only rows satisfying the WHERE clause (if it is present). So, the fact that the insert is being done doesn’t mean the update will for sure affect some row, because it have a WHERE clause that needs to be satisfied.

The WHERE clause of the update statement is key here.

]]> By: inprise http://itknowledgeexchange.techtarget.com/itanswers/plsql/#comment-60041 inprise Wed, 18 Feb 2009 09:06:31 +0000 #comment-60041 Hello,

Yes i checked with sqlcount — its don’t hav rows to update,but the update column and INSERT column on second table are same,defeintly if record Insert happening,UPDATEshould also happen

It looks strange

Any table creation criteria stops from this update??

]]> By: carlosdl http://itknowledgeexchange.techtarget.com/itanswers/plsql/#comment-59990 carlosdl Tue, 17 Feb 2009 13:41:17 +0000 #comment-59990 Remember to set serveroutput on if you run your procedure from sql*plus.

]]>