Caution | Inside Oracle APEX by Patrick Wolf

Caution with new “Runtime Where Clause” in Oracle APEX 3.1

22. May 2008

Found out the hard way that the new property “Runtime Where Clause” for processes (eg. Fetch, DML) has a serious bug. The value of the property gets exported and is contained in the export file of an application, but it isn’t set when you import an application!!! Because most of us are not developing on the [...]

Caution: Apex_Item.Date_Popup and Oracle APEX 3.1

25. March 2008

2 Comments

Just to let you know in case you are hitting the following problem or plan to upgrade to 3.1. The version of Apex_Item.Date_Popup which comes with Oracle APEX 3.1.0.00.32 has a “small” bug. The Date Picker will always write the return value into the first row, independent for which row you have opened the Date [...]

Attention! Are you using the Drop in replacement for V and NV function?

12. March 2008

7 Comments

If you are using my Drop in replacement for V and NV function and you are upgrading to Oracle APEX 3.1 then you have to alter the functions to reference the new schema FLOWS_030100!!! If you are not doing this your applications will not work because the functions are trying to read the session state from [...]

Warning: DBMS_LDAP.simple_bind_s/ APEX_LDAP.authenticate and NULL password

10. January 2008

12 Comments

Just came across a very strange behavior of the DBMS_LDAP.simple_bind_s and APEX_LDAP.authenticate procedure which I used to do a basic LDAP authentication against our MS Active Directory server. I used the following simple test code

SQL embedded into PL/SQL

23. October 2007

0 Comments

A few days ago I spoke with another developer about SQL embedded into PL/SQL code and how function calls are handled in the WHERE clause of SQL statements. There is sometimes confusion who (PL/SQL engine or SQL engine) is executing it, I thought it’s a good idea to write a posting about it. Last year I [...]

Lock conflicts with Automatic Row Processing (DML)

2. May 2007

0 Comments

Oracle APEX 3.0 contains a nice new feature you should be aware of. There is a new substitution variable APEX_DML_LOCK_WAIT_TIME which you can use to define how the behavior of the “Automatic Row Processing (DML)” and ApplyMRU/D processes should be in case if the processed row is locked.

Slightly different behavior of $x in Oracle APEX 3.0

25. March 2007

1 Comment

Just noticed a slightly different behavior of $x in Oracle APEX 3.0. Probably many of you just use it to pass the id-string of an element (eg. $x(”P4_TEST”)) to this function to get the object of this field/div/… id, but you can also call it with an object and in that case the function will just [...]

Incomplete/Broken HTML output

27. February 2007

0 Comments

A few days ago an ApexLib user from Norway contacted me and told me that the framework doesn’t work and he is getting JavaScript errors. I looked at the provided HTML output and I was scratching my head, because the output looked really strange and I couldn’t really come of with a good reason why the [...]

Referencing non existing APEX items

30. November 2006

0 Comments

Did you know that when you reference a non existing APEX item in your SQL statements or PL/SQL code, that you are not getting a runtime error? APEX will just return NULL in such a case!

APEX items and implicit type conversion

29. November 2006

0 Comments

Be aware when using bind variables or the V function to reference an Oracle APEX item in your SQL statements or your PL/SQL code that APEX/Oracle always stores this values as VARCHAR2’s in its internal arrays!

Archive | Caution RSS feed for this section