RE: Database programming standards

We are undergoing this battle. The project that I am assigned to hired 
contractors who brought in pl/sql programmers and put 90% of the logic and 
business rules in the backend implemented as pl/sql.  Now the project end is in 
sight and all the full-time staff programmers (hired more recently) are .net 
programmers who want to rip it all out and put it into the front end. Why?  
"Because the job will be much easier long-term after they are gone."<g>



> One standard that I would insist on is that *all* sql will be 
> written in
> PL/SQL (stored packages, procedures and functions).  The J2EE 
> classes can
> simply call these objects to perform the sql operation.  This 
> solves all of
> the bind variable problems.  Of course, this means that they will need
> oracle back-end specialists.  But it will make your job much easier
> long-term after they are gone.
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Other related posts: