Exception not raised

Question

heloo...
i had 1 procedure for inserting value. when i call that procedure it doesnot raise exception evenif there is error.
any one can help me out ...........................

Answer 1

>>Passing that many parameters across is looking for problems. It is very easy to
transpose parameters when there are more than 3 or 4 parameters. This proc has 14.Can you explain this sir in detail
When a programmer needs to call you stored proc with 14 parameters, he must be very careful in placing his variables and values in the right sequence to ensure that the right variable/value is passed to the right parameter.
A good programmer will not take a chance and code 14+ lines of code for this procedure call, e.g.
begin
... code ..
SPINSERTATTRIBUTE(
AttributeId => var1,
Name => var2,
Label => var3,
Description => var4,
Category => var5,
Datatype => var6,
MinValue => var7,
MaxValue=> var8,
DefaultValue => var9,
AllowNull => var10,
Enumeration => var11,
Len => var12,
Scale => var13,
Values=> var14,
Result => var15
.. code...
end;Now this is a lot of code to write. Easy to get the sequence wrong. A not-so-good programmer will be lazy and will instead code this - which is even more dangerous as it is a lot easier to get the parameter sequence wrong:
begin
..code..
SPINSERTATTRIBUTE( var1, var2, var3, var5, var6, var8, var7, var9, var10, var11, var12, var13, var14 );
.. code..
end;Do not make it complex and difficult for others (and yourself) to call a procedure/function.method that you have written.
> Is there possible to pass any number of argument while calling the procedure with
argument type as %rowtype?
Do not understand the question... A procedure can in theory contain unlimited parameters (there could be some pratical limitations in PL/SQL though).
%ROWTYPE is no different that a C struct definition or a Pascal/Delphi record definition.
%ROWTYPE is a special definition that tells the PL/SQL engine that the variable is a record structure that matches the layout of a specific SQL table.
It is easy to use as the definition of the structure is defined once - it is the definition of the SQL table. If the DBA adds a column or drops a column, your record structure definition in PL/SQL does not need to be manually changed.
Typically a caller will call the sample stored procedure InsertAttribute I wrote as follows:
attrRow attributes%ROWTYPE;
begin
-- create a new attribute
attrRow.Name := 'SHIPPING COSTS';
attrRow.Datatype := 'NUMBER';
.. etc..
InsertAttribute( attrRow );
.. code ..
end;