Pragma

{\rtf1\ansi\ansicpg1252\deff0\deflang16393{\fonttbl{\f0\froman\fprq2\fcharset0 Times New Roman;}{\f1\fnil\fcharset0 Calibri;}}
{\*\generator Msftedit 5.41.21.2509;}\viewkind4\uc1\pard\li720\lang1033\f0\fs18 A pragma is a directive to the PL/SQL compiler. Pragmas pass information to the compiler; they are processed at compile time but do not execute. If you include a call to a built-in package in a SQL statement, you must include a RESTRICT REFERENCES pragma in your code. This pragma tells the compiler the purity level (freedom from side effects) of a packaged program.\par
\par
Pragma keyword is used to give instructions to the compiler. There are 4 types of Pragmas:\par
\pard\fi-360\li1080\tx1080 A)\tab Exception_Init: - Tells the compiler to associate the specified error number with an identifier that has been declared an Exception in your current program or an accessible package.\par
\pard\fi-360\li1080 B)\tab Restrict_References: - Tells the compiler the purity level of packaged program. The purity level is the degree to which a program does not read/write database tables and/or packaged variables.\par
C)\tab Serially_Reusable: - Tells the runtime engine that package data should not persist between references. This is used to reduce per-user memory requirements when the package data is only needed for duration of call and not the duration of session.\par
\pard\sa200\sl276\slmult1 Autonomous_Transactions: - Tells the compiler that the function, procedure, top-level anonymous P/L SQL block, object method, or database trigger executes in its own transaction space.\lang9\f1\fs22\par
}