Re: Java vs PLSQL

Well,

IMHO, PL/SQL is the language of choice when it comes to data processing since Java (no matter if it's external or running in JServer) uses JDBC for interacting with the server thus wasting time for translation. PL/SQL is executed right away just like plain SQL (and even doesn't need compilation step if it's not anonymous) reducing the response time greatly.

As of PSP vs JSP - we were trying both and finally came up with Dynamic PSP which is a natural extension to Oracle PSP plus adds quite a lot of features Oracle's implementation lacks:
- everything is stored in the database and edited thru a web interface
  (that is, any HTML 4.0x browser can serve as an editor), DPSP itself   is written in PL/SQL ( ;P to those saying that PL/SQL is not good   for string processing/manipulation );
- runs everywhere Oracle runs (because we don't need anything beyond
  Oracle server) unlike cartridge approach;
- doesn't limit number of parameters one can pass into a DPSP page
  (no parameter declarations required, thus giving you greater   flexibility in parameter passing - you can omit optional parameters,   you can easily change code to accept more parameters than initially   planned by simply referencing them where they are needed, etc.);
- each DPSP page can 'call' any other page and either embed its output
  right away (procedure form) or get the output into a string, string   array or CLOB and process it further (function form) thus allowing   effective code reuse (you can code common objects, for example,   for page header/footer, hit counter or anything, and then embed   them in other pages as needed);
- DPSP objects can be ran as anonymous PL/SQL blocks (great for
  debugging but adds some overhead for compilation before execution),   or compiled into packages (for example, for subsequent wrapping and   distribution, or for finalizing changes);
- each object can be created with either definer or invoker rights
  to better maintain security, grants/synonyms creation is handled   automatically by DPSP interpreter/compiler engine;
- a set of predefined functions and procedures is added for easy
  parameter/environment vars retrieval, profiling, debugging, and   flow control.

JSP, Perl and others are all good tools for web development in general, but they are all file-based. If you need to change one character you have to edit the file and reupload it back to server. With DPSP you just open your browser, open the object source, edit it, hit save button - and you're done. Next time the object is called, new copy will be executed. This really speeds up development as we experienced in our own environment.

If you are interested in seeing Dynamic PSP in action, please visit http://www.dpsp-yes.com and either try the live demo or download yourself a trial copy and install it, play with it and decide if it's good for you. By the way, the site itself is done with Dynamic PSP (except the index page which redirects to the DPSP engine :)

best regards,

    Bob. Received on Sun Jul 22 2001 - 01:54:11 CDT