server side package or emrbace Apex and use its capability
812369Mar 9 2012 — edited Mar 9 2012This may not be a suitable question for this forum but I can only try.
My experience with APEX is primarily doing everything in the APEX “front end” and only calling PL/SQL packages in the database when absolutely necessary.
A colleague insists on putting everything in a PL/SQL package in the database and putting calls in APEX to functions & Packages.
One example I can quote is we had a conditional tab which could only be viewed if you had an entry in a table.
I did the SQL code for the tab in the conditions section in apex. My colleague then reworked my code to call a PL/SQL package and placed the code I had written on the server.
Another example was a demo of lazy load on an input field he loved it but then when he realised it could not be done via a call to a server side package dismissed the lazy load idea as not relevant even though it would make our users life easier.
I am soon to have a battle royal over which is the best approach. Any comments.