Skip to Main Content
Forums

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Oracle APEX 5.1 Interactive Grid - LOV contents should be different for each row

franklin.jrJan 31 2017 — edited Feb 13 2017

Dear friends, I have an interactive grid for Oracle APEX 5.1 and one of its columns has an LOV.

This LOV is based on a SQL query which invokes, among other criteria, a package.function with parameters such as : CD_ITEM1 and : CD_ITEM2 from other columns at the same interactive grid, as well as : P1_CD_PARAMETER and : P2_CD_PARAMETER which are page items.

It should pop up a LOV which displays, for example, 1, 2, 3 depending on parameters at one row, and 4, 5, 6 depending on parameters at another row.

However, this LOV does not seem to work - it does not filter any value in any column and it brings all LOV values for each row. Do you know any reason for that?

Thanks in advance.

Comments

Ramin Hashimzadeh

Read Study Guide for

1Z0-144: Oracle Database 11g:Program with PL/SQL

Handling PL/SQL Errors

You can also treat particular messages as errors instead of warnings. For example, if you know that the warning message PLW-05003 represents a serious problem in your code, including 'ERROR:05003' in the PLSQL_WARNINGS setting makes that condition trigger an error message (PLS_05003) instead of a warning message. An error message causes the compilation to fail.

----

Ramin Hashimzade


MartijnBos

Why are you asking?

If I were you, I would just try out, and see wat happen.

813048

Thanks for your reply.

I dont know how to test this scenario.Can you tell me the codes how to try/test the same.

MartijnBos

Have a look at this page from the doumentation.

(search for severe)

Then you can create your on test-code.

813048

Which document?

Hoek

This:

Oracle Database Online Documentation 11g Release 2 (11.2)

(use the search box)

the 2-Day Developers Guide would be a good starting point to explore: Contents along with the SQL reference: Contents

813048

I am not able to find the answer from the document.

Can you tell me what will be the answer for this and why(reason)?

Waiting for your help.

Hoek

This should clear things up for you:

PLSQL_WARNINGS

PLW-05000 to PLW-07206

1 person found this helpful
813048

Hello Hoek,

From your ref. document what i understand answer will be-

C. It issues warnings whenever the code causes an unexpected action or wrong results performance problems.


Am i correct?

INRi

yes you are correct..whenever you will get performance issue it issues warnings with error msg  05003.

1 person found this helpful
Hoek

No, it is B, you'll get a compilation error, instead of a warning, your object will not compile:

SQL> ALTER SESSION SET plsql_warnings = 'enable:severe','enable:performance';




Session altered.




SQL> create function unreachable


  2  return varchar2


  3  as


  4   i_am_unreachable varchar2(1);


  5  begin


  6   return 'Y';


  7   i_am_unreachable := 'Y';


  8  end;


  9  /




SP2-0806: Function created with compilation warnings




SQL> sho err


Errors for FUNCTION UNREACHABLE:




LINE/COL ERROR


-------- -----------------------------------------------------------------


1/1      PLW-05018: unit UNREACHABLE omitted optional AUTHID clause;


         default value DEFINER used




SQL> ALTER SESSION SET plsql_warnings = 'enable:severe','enable:performance', 'ERROR:06002';




Session altered.




SQL> create or replace function unreachable


  2  return varchar2


  3  as


  4   i_am_unreachable varchar2(1);


  5  begin


  6   return 'Y';


  7   i_am_unreachable := 'Y';


  8  end;


  9  /




Warning: Function created with compilation errors.




SQL> sho err


Errors for FUNCTION UNREACHABLE:




LINE/COL ERROR


-------- -----------------------------------------------------------------


1/1      PLW-05018: unit UNREACHABLE omitted optional AUTHID clause;


         default value DEFINER used




7/2      PLS-06002: Unreachable code


SQL>

Message was edited by: Hoek I just noticed: Ramin already pointed this out in the first reply you got on your thread. Hope it is all 100% clear now.

Hoek
Answer

No, that is not correct.

It will turn WARNING 5003 into an ERROR, causing compliation to fail instead of succeed. And it has totally nothing to do with performance.

Marked as Answer by 813048 · Sep 27 2020
1 person found this helpful
1 - 12
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Mar 13 2017
Added on Jan 31 2017
#apex-discussions
6 comments
2,797 views