Term
|
Definition
| A small bit of logic defined by you, to instruct a particular table about how it will accept, modify, or reject incoming data. |
|
|
Term
|
Definition
| A structure that can store data. All data is structured in columns and rows. Each column’s datatype is explicitly defined. |
|
|
Term
|
Definition
| An object designed to speed up searches in a table. An INDEX performs much the same way as an index to a book, by copying a relatively small, select amount of information, sorting it for speedy reference, and tying it back to locations in the table for supporting quick lookups of rows in the source table. |
|
|
Term
|
Definition
| A “filter” through which you can search a table, and interact with a table, but that stores no data itself, and simply serves as a “window” onto one or more tables. VIEW objects can be used to mask portions of the underlying table logic for various reasons—perhaps to simplify business logic, or perhaps to add a layer of security by hiding the real source of information. A VIEW can be used to display certain parts of a table, while hiding other parts of the same table. |
|
|
Term
|
Definition
| A counter, often used to generate unique numbers as identifiers for new rows as they are added to a table. |
|
|
Term
|
Definition
| An alias for another object in the database, often used to specify an alternative name for a table or view. |
|
|
Term
|
Definition
| The “owners” of database objects. |
|
|
Term
|
Definition
| A set of one or more privileges that can be granted to a user. |
|
|
