Comments on: PRAGMAtism in Oracle PL/SQL

By: Eddie Awad

Eddie Awad — Mon, 10 Dec 2007 20:26:22 +0000

@John: I have used PRAGMA SERIALLY_REUSABLE in real life. In fact, it is in use in one of my production PL/SQL packages today. Here is a related post and comments:

http://awads.net/wp/2007/04/04/here-is-how-to-unpersist-your-persistent-plsql-package-data/

By: John

John — Mon, 10 Dec 2007 19:27:56 +0000

This blog post is giving me a flashback of trying to formulate the explanation for PRAGMA SERIALLY_REUSABLE in the PL/SQL Guide. I’m still wondering if it’s ever needed in real-life situations.

By: kranthi

kranthi — Sat, 14 Apr 2007 05:49:10 +0000

Hello Sir,
Your blog helped me gain knowledge about existing Pragma’s but
i would like to know if Oracle uses any COMPLIER as such for compiling the Pl/SqL programs

By: About The BUILTIN, FIPSFLAG and INTERFACE Pragmas in Oracle » Eddie Awad’s Blog

Wed, 24 May 2006 20:15:03 +0000

[…] A few weeks ago I blogged about PRAGMAs in PL/SQL. As you all know, as of the current release of PL/SQL, we have 4 documented pragma directives: AUTONOMOUS_TRANSACTION, RESTRICT_REFERENCES, EXCEPTION_INIT and SERIALLY_REUSABLE. […]

By: Karl

Karl — Thu, 18 May 2006 16:31:46 +0000

Hi! building new 10.2 instance is saw other pragmas srcolling on my console ... * building the standard package the BUILTIN Pragma :

create or replace
  2  package STANDARD ...
   function "EXISTS" return BOOLEAN;
235      pragma BUILTIN('EXISTS',10,240,240); -- This is special cased in PH2 -- Pj

the FIPSFLAG Pragma ...

function SQLERRM (code PLS_INTEGER) return varchar2;
294      pragma BUILTIN('SQLERRM',46, 10, 1); -- PEMS_DB, DB_SQLERRM
295      pragma FIPSFLAG('SQLERRM', 1452);

the INTERFACE Pragma ...

2734   --#### All user-visible declarations should preceed this point.  The
2735    --#### following are implementation-oriented pragmas that may need
2736    --#### editing in the future; we would prefer to be able to edit them
2737    --#### without affecting the rft numbering of user-visible items.
2738  
2739    --#### interface pragmas
2740  
2741    --#### Note that for any ICD which maps directly to a PVM
2742    --#### Opcode MUST be mapped to pes_dummy.
2743    --#### An ICD which invokes another ICD by flipping operands is
2744    --#### mapped to pes_flip, and an ICD whose result is the inverse of
2745    --#### another ICD is mapped to pes_invert
2746    --#### New ICDs should be placed at the end of this list, and a
2747    --#### corresponding entry must be made in the ICD table in pdz7
2748  
2749    PRAGMA interface(c,length,"pes_dummy",1);
2750    PRAGMA interface(c,substr,"pes_dummy",1);
2751    PRAGMA interface(c,instr,"pesist",1);
2752    PRAGMA interface(c,UPPER,"pesupp",1);
2753    PRAGMA interface(c,LOWER,"peslow",1);

Do not know what they mean and if thy can be used in user pl/sql Code. Greetings Karl