![]() (You will be able to do so with PL/SQL Release 2.2 and above this release runs against Oracle7 Server Release 7.2, which contains the hooks for the step debugging in PL/SQL.) (This restriction applies only to PL/SQL Version 2.0 this restriction goes away in Release 2.1 and beyond.)Ī stored procedure called from Oracle Developer/2000 cannot have only OUT argument types.įrom Oracle Developer/2000, you can call stored procedures, but you cannot debug them from within the Oracle Developer/2000 tool. You must provide an argument for each parameter in a stored module's parameter list, even if that parameter has a default value. ![]() You cannot directly execute remote procedure calls using the standard syntax You cannot directly reference a package object using the dot notation. Only four datatypes are supported for module parameters: DATE, VARCHAR2, BOOLEAN, and NUMBER. ![]() The end result is a mechanism which:ĭoes not require any changes to the PL/SQL Version 1.1 base productĭoes allow the Oracle Developer/2000 application to find and execute stored proceduresĭoes not require any special syntax to distinguish between stored and local PL/SQL modulesĪchieving this effect, however, imposes several restrictions on the use of stored procedures: In the meantime, the tools group at Oracle Corporation has had to come up with a way to allow applications based on Oracle Developer/2000 to call stored procedures in the most transparent fashion possible. The PL/SQL version inside the Oracle Developer/2000 tools will be upgraded to PL/SQL Release 2.3 sometime in 1998 with Release 2 of Oracle Developer/2000. The Oracle Developer/2000 tools use PL/SQL Version 1.1, while the PL/SQL versions on the server range from 2.0 to 8.x. Restrictions on Calling Stored Procedures ![]() Using Stubs to Talk to Server-Side PL/SQL ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |