- What is Dynamic PSP?
- What are the differences between Oracle PSP and Dynamic PSP?
- Why not use JSP?
- Why Oracle still supports PL/SQL when they integrated Java into Oracle RDBMS?
- How To Secure Dynamic PSP Development Interface?
- How to enable native PL/SQL compilation in 9i Release 2 on Windows?
- I am unable to login into Unit Commander using default account.
- What is WebDAV?
- How to avoid redirection from index.html to DPSP unit?
- Java class to convert xls to csv or from MS Excel to CSV file into PL/SQL and upload data from .xls file to Oracle
- Java class to convert from DBF (DB2) to CSV file within Oracle PL/SQL
What are the differences between Oracle PSP and Dynamic PSP?
Although Oracle has a term 'PSP' with the same meaning of 'PL/SQL Server Pages',
it differs seriously from our DPSP implementation. After a bit of playing with
Oracle's PSP we decided that it is lacking the functionality we needed,
so we decided to create our own server-side extension to Oracle RDBMS/AS and
devised it Dynamic PSP as this abbreviation best describes what we intend to
achieve but sets us aside from Oracle's PSP approach. We believe DPSP is a viable
alternative to Oracle's PSP as well as JSP, because it doesn't require experienced
Oracle PL/SQL programmers to learn Java and doesn't limit them in the way they can
get things done. DPSP shares common syntax with Oracle's PSP, but extends it with
some helpful features, like a number of predefined functions, dynamic execution (unlike
Oracle's one-time compilation approach), unlimited number of parameters to any DPSP
object (in PSP, number of parameters is fixed), and more.
In Oracle PSP you write a dynamic page as a text file and then use a special utility
that parses your page, creates a package and loads/compiles that package into Oracle RDBMS.
Each external parameter you define in PSP page becomes a parameter of the procedure in the
package. This limits number and names of external parameters for this particular PSP page.
Each time a change in functionality of the page is required, you need to edit the source file
and reload the page into Oracle. On the contrary, each DPSP block is stored in the database, it has
unique numeric identifier (ID) and unique string name, and it is parsed and compiled dynamically
when accessed. These blocks are called DPSP units. DPSP unit can represent a complete page or
a logical block (subroutine) that can be called from another DPSP unit. DPSP units can be
called from each other either by ID or by name, and can accept unlimited number of external named
parameters. DPSP units are dynamically parsed and compiled and all changes you made to them
become instantly available. DPSP units can also be compiled into packages
(in fact, this is a mandatory step for publishing a unit when recommended secure setup procedure is followed).