Powell, Mark D apparently said,on my timestamp of 13/04/2005 11:23 PM: > I think Tom Kyte of asktom fame wrote a response on this topic that said if > he was going to design a database independent application he would write a > web interface without any SQL calls. Instead all SQL would be encapsulated > in procedure calls that pass back cursors. This was you just write a > database specific procedure for each port: Oracle, DB2, SQL Server, etc.... > > Naturally this makes any database without stored procedures a non-choice for > the product. > > I kind of like this design idea. > Not just Tom. I did two designs for the RAAF back in 2001 where there was not a single SQL anywhere. All PL/SQL calls, API-style, 8ir3 on a J2EE Websphere-based application, using PL/SQL record types to transfer data in/out. Not a single EJB in sight, pure DAOs. Still the best performing NT-based applications in the local Air Force. By a country mile. The method works and works good. It also shields the code from minor underlying database changes. And makes life a lot easier for the db designer. Ah yes: we also used XML to extract the definitions of all that and pass them back to the Websphere developers so they could build their DAOs using the latest. -- Cheers Nuno Souto in sunny Sydney, Australia dbvision@xxxxxxxxxxxx -- //www.freelists.org/webpage/oracle-l