RelationalDBDesign 


PL-SQL Stored Objects Glossary

Back to root Glossary
A B C D E F G H I J K L M N  O  P Q R S T  U V W X Y Z 
Data integrity
The completeness and accuracy of data, including the validity of relationships between rows in related tables
Function
A function is a set of PL/SQL code that is stored inside the database with a name. A function always returns a value. A function can use incoming parameters, but not outgoing parameters.
Lock
A marker imposed on a table or a row that prevents concurrent updates on the same table or row.
Lock level
The level to which a particular lock is imposed. Lock level can be either row (lock applies to one or more rows in a table), or table (lock applies to an entire table).
Lock mode
The source of the lock. Lock mode can be implicit (created automatically by the database) or explicit (imposed by program code.)
Object Privileges
These privileges allow a user to see objects
Package
A stored sub-program that combines PL/SQL procedures and functions into a single unit.
Package body
The portion of the package that defines to underlying procedures and functions. In addition, other functions and procedures that are private (for use only within the package) may be defined.
Package specification
The portion of the package that defines all public (callable) procedures and functions including their parameters.
Parameter
A value passed to a PL/SQL stored object when it is executed. All types of PL/SQL stored objects except triggers can use parameters. Cursors also can use parameters. Parameters can be of nearly any datatype that can be defined within PL/SQL.
Privilege
Permissions to either perform tasks or access data in the database
Role
A grouping of privileges that is given a name
Stored function
A function that is stored as a named object in the database.
System privileges
These are permissions to do certain tasks in the database. For example, the capability to create a table is a system privilege.
Transaction control
A command used inside PL/SQL to tell Oracle when one transaction starts and ends. For example, the COMMIT command ends a transaction.
Trigger
A stored sub-program that is similar to a procedure and is automatically executed by the database whenever a specified action occurs. The timing of a trigger specifies whether the trigger is executed before or after the action. The action of a trigger specifies activity in the database, such as a user updating one or more rows in a table. The scope of a trigger specifies whether the trigger fires once per row or once per transaction.