What is the correct definition of the persistent state of a packaged variable?
A.
It is a private variable defined in a procedure or function within a package body whose value is consistent within a user session.
B.
It is a public variable in a package specification whose value is consistent within a user session.
C.
It is a private variable in a package body whose value is consistent across all current active sessions.
D.
It is a public variable in a package specification whose value is always consistent across all current active sessions.
B
Yes:B
Wy it can’t be D?
Because package’s variable’s value consistent across only envoker’s session. (lalala)
B
Persistent states in package variables and cursors
o You can keep track of the state of a package variable or cursor, which persists throughout the user session, form the time the user first references the variable or cursor to the time the user disconnects.
o It persists across transactions within a session
o It does not persist from session to session for the same user.
o The value of the variable is released when the user disconnects.
o Each session will have its own value for the variables.
o It persists across the transactions and through the user session.
o Reusable package will last only for each database call.
o PRAGMA SERIALLY_REUSABLE;
o Serially reusable version resets the state (and thus the output) each time.
o By the first time you call a procedure, function, or reference a global variable within the package, the whole package will be loaded into the memory and stay there.
B
B
B