Progress
DataServer
for ORACLE Guide
Compiling Progress Procedures
The COMPILE statement lets you compile Progress procedures and save the compilations to disk. This speeds up your application since Progress does not have to recompile it every time you want to run a procedure.
To compile procedures that access an ORACLE database, start up Progress and connect to the schema holder for your target ORACLE database using the schema holder’s logical database name. Then use the COMPILE statement. If you change the name of the schema holder after compiling a procedure, you must connect to the renamed schema holder and recompile the procedure. You do not have to connect to the target ORACLE database to compile a procedure. For more information, see the COMPILE Statement reference entry in the Progress Language Reference.
R-code
The compiled r-code is portable among like user interfaces. For example, code that you compile in character mode on a Sun machine can run on any other UNIX machine in character mode. Code compiled on Windows 95 can run on NT or Windows 98. But code compiled on Windows cannot run in character mode on a Sun machine.
The r-code is not portable among database management systems. For example, code that you have compiled for an ORACLE database will not run with a Progress database.
The size of r-code grows when you compile procedures against an ORACLE database as compared with compiling against a Progress database. The r-code for a DataServer application contains as text the portions of SQL statements that the DataServer passes to ORACLE.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |