StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13549779
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-11-25T09:30:38.043
FavoriteCount
0
LastActivityDate
2012-11-25T10:15:25.453
LastEditDate
2012-11-25T10:15:25.453
LastEditorUserId
458741
OwnerUserId
458741
ParentId
13548891
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Your problem is actually caused by your check: <pre><code> SELECT COUNT (cus_code) INTO value_check FROM customer WHERE cus_code = temp_ccode; </code></pre> The above query will never return NULL, which is what you are checking for. If no values in the table match the parameter <code>temp_ccode</code> then the <code>value_check</code> will be 0. This in turn means your IF statement is incorrect and this causes your error later in your code. There's a simpler and more efficient way of doing this though. You can use <a href="http://docs.oracle.com/cd/E11882_01/appdev.112/e25519/static.htm#LNPLS528" rel="nofollow">SQL%ROWCOUNT</a> to find out how many rows were effected by your UPDATE. If the return value is 0 then your customer doesn't exist. <pre><code>create or replace procedure cust_pay ( Ptemp_ccode in number , Ppay_amount in number ) is l_balance number; begin update customer set cus_balance = cus_balance - Ppay_amount where cus_code = Ptemp_ccode; if SQL%ROWCOUNT = 0 then dbms_output.put_line('The customer was not found.'); else select cus_balance into l_balance from customer where cus_code = temp_ccode; if l_balance < 0 then dbms_output.put_line('the client owes us ' || l_balance); else dbms_output.put_line('customer new balance is ' || l_balance); end if; end if; end; </code></pre> There's no need to handle the NO_DATA_FOUND exception in the <code>select... into ...</code> here as you've already guaranteed that the <code>cus_code</code> exists by your UPDATE statement. Please note the other changes I've made: <ol> <li>Different naming conventions for parameters and variables so it's clear in the code which is which.</li> <li>Removal of the additional nested PL/SQL block, which was unnecessary.</li> </ol> Generally speaking you should never use <code>dbms_ouput.put_line</code> in a PL/SQL block as you have to be there to see what's happening. It's fine for debugging processes but is fairly useless in production code. It's also possible to use the <a href="http://docs.oracle.com/cd/E11882_01/appdev.112/e25519/return_statement.htm#LNPLS01340" rel="nofollow">RETURN statement</a> to avoid the nested IF statements, which I think makes the code cleaner and easier to read; though this is a judgement call. <pre><code>create or replace procedure cust_pay ( Ptemp_ccode in number , Ppay_amount in number ) is l_balance number; begin update customer set cus_balance = cus_balance - Ppay_amount where cus_code = Ptemp_ccode; if SQL%ROWCOUNT = 0 then return; end if; select cus_balance into l_balance from customer where cus_code = temp_ccode; if l_balance < 0 then dbms_output.put_line('The client owes us ' || l_balance); else dbms_output.put_line('New balance is ' || l_balance); end if; end; </code></pre> All of this assumes that your CUSTOMER table is unique on <code>cus_code</code>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to check parameter value existence in a procedure?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USBen
UserOwnerUserId
1. USBen
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to check parameter value existence in a procedure?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.