StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16680995
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-05-21T23:10:49.210
FavoriteCount
0
LastActivityDate
2013-05-31T14:14:11.247
LastEditDate
2013-05-31T14:14:11.247
LastEditorUserId
58371
OwnerUserId
58371
ParentId
16680746
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Your input parameter <code>%type</code> statements claim the column names are <code>col_name</code> and <code>col_price</code>. But that is not how you refer to them in your stored procedure (<code>name</code> and <code>price</code>). Bad things can happen when you name variables after column names. <a href="http://asktom.oracle.com/pls/apex/f?p=100:11:0%3a%3a%3a%3aP11_QUESTION_ID:6729304326802" rel="nofollow">AskTom</a> recommends a limited convention of variable naming conventions: <ul> <li>local variables start with <code>L_</code></li> <li>parameters start with <code>P_</code></li> <li>global package variables start with <code>G_</code></li> </ul> That link has a good general discussion on PL/SQL naming conventions. I personally just use <code>V_</code> for most variables (aside from indexes and other obvious things), but that's just me. Lastly, the <code>col_</code> in the column names seem redundant; simply use <code>name</code> and <code>price</code> as column names. So, that said, I think this does what you want: <pre><code>create table table1 ( name varchar2(30), price number ); create or replace procedure TEST( p_name IN table1.name%type, p_price IN table1.price%type ) is begin update table1 set name = p_name where price = p_price; commit; end TEST; / insert into table1 values ('John', 500); commit; select * from table1; exec TEST(p_name => 'Bob', p_price => 500); select * from table1; -- Clean up test artifacts drop procedure test; drop table table1; </code></pre> Giving the output: <pre><code>table TABLE1 created. PROCEDURE TEST compiled 1 rows inserted. committed. NAME PRICE ------------------------------ ---------- John 500 anonymous block completed NAME PRICE ------------------------------ ---------- Bob 500 procedure TEST dropped. table TABLE1 dropped. </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POpl /sql procedure execution giving an error
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USstv
UserOwnerUserId
1. USstv
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POpl /sql procedure execution giving an error
 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
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.