Oracle PL/SQL Language Pocket Reference- P19: This pocket guide features quick-reference information to help you use Oracle's PL/SQL language. It includes coverage of PL/SQL features in the newest version of Oracle, Oracle8i. It is a companion to Steven Feuerstein and Bill Pribyl's bestselling Oracle PL/SQL Programming. Updated for Oracle8, that large volume (nearly 1,000 pages) fills a huge gap in the Oracle market, providing developers with a single, comprehensive guide to building applications with PL/SQL and building them the right way. . | ORA-06571 Function TOTAL_COMP does not guarantee not to update database As discussed in Section Realities Calling PL SQL Functions in SQL it can be very difficult at times and sometimes impossible to avoid this error. In other situations however there is an easy resolution certainly do check the above list of restrictions . Previous Requirements for Stored Functions in SQL Requirements for Stored Functions in SQL Oracle PL SQL Programming 2nd Edition Book Index Next Calling Packaged Functions in SQL Calling Packaged Functions in SQL The Oracle Library Navigation Copyright c 2000 O Reilly Associates. All rights reserved. Please purchase PDF Split-Merge on to remove this watermark. Previous Restrictions on PL SQL Functions in SQL Chapter 17 Calling PL SQL Functions in SQL Next Column Function Name Precedence Calling Packaged Functions in SQL As I describe in Chapter 16 Packages the specification and body of a package are distinct a specification can and must exist before its body has been defined. This feature of packages makes life complicated when it comes to calling functions in SQL. When a SELECT statement calls a packaged function the only information available to it is the package specification. Yet it is the contents of the package body which determine whether that function is valid for execution in SQL. The consequence of this structure is that you will have to add code to your package specification in order to enable a packaged function for calling in SQL. To use the official lingo you must explicitly assert the purity level the extent to which a function is free of side effects of a stored function in a package specification. The Oracle Server can then determine when the package body is compiled whether the function violates that purity level. If so an error will be raised and you then face the sometimes daunting task of figuring out where and how the violation occurs. You assert a purity level for a .
