| Oracle® PL/SQL® Interactive Workbook, Second Edition
By
Benjamin Rosenzweig, Elena Silvestrova
| | Table of Contents | |
Appendix A.
Answers to Self-Review Questions |
Chapter 19 Records
Lab 19.1 Self-Review Answers | | A1:
| |
1) |
C |
%ROWTYPE means "based on a row." This row may be based on a database table row or on a row returned by a cursor. |
| | | A2:
| |
2) |
C |
When a field with a NOT NULL constraint is not initialized, a user-defined record causes an error. |
| | | A3:
| |
3) |
B |
You are able to assign a table-based record to a cursor-based record and vice versa. This restriction applies to user-defined records that have the same structure yet different data types. |
| | | A4:
| |
4) |
A |
An aggregate assignment statement between two user-defined records causes an error where the records are not based on the same type. |
| | | A5:
| |
5) |
B |
A table-based record can be assigned to a user-defined record as long as they have the same structure. This restriction applies to user-defined records that have the same structure yet different data types. |
|
Lab 19.2 Self-Review Answers | | A1:
| | | | A2:
| | | | A3:
| |
3) |
C |
You must initialize each field that has a NOT NULL constraint specified on it regardless of the record type. |
| | | A4:
| |
4) |
B |
A nested record may contain any collection as one of its fields. |
| | | A5:
| |
Lab 19.3 Self-Review Answers | | A1:
| | | | A2:
| |
2) |
B |
A varray has an upper bound that can be extended to its maximum size. The data type of its individual elements has no effect on how the upper bound is extended. |
| | | A3:
| |
3) |
B |
You must always initialize a nested table regardless of its element type. |
| | | A4:
| |
4) |
B |
You must always increase the size of a nested table before populating it with a new record regardless of its element type. |
| | | A5:
| |
5) |
B |
You can use user-defined, table-based, or cursor-based records when creating a collection of records. |
|
|
|
| |
No comments:
Post a Comment