Record (File architecture): Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 13: | Line 13: | ||
== The Structure of a Model 204 Record == | == The Structure of a Model 204 Record == | ||
=== Extension Pointer === | |||
=== Data === | |||
<p>If there are any preallocated fields in a file (see the [[OCCURS attribute]]) every record in that file will begin with the set of such fields. The set of fields is stored in the Record Map in [[Table D (File Architecture)|Table D]].</p> | <p>If there are any preallocated fields in a file (see the [[OCCURS attribute]]) every record in that file will begin with the set of such fields. The set of fields is stored in the Record Map in [[Table D (File Architecture)|Table D]].</p> | ||
| Line 31: | Line 37: | ||
==== Large Objects Without Table E ==== | ==== Large Objects Without Table E ==== | ||
[[Category:File Architecture and Management]] | |||
[[Category:File Architecture]] | |||
Revision as of 02:57, 4 April 2013
A Model 204 Record is a collection of fields (either individually or in Repeating Field Groups (RFGs)).
Each record is variable in length and need contain only the fields that pertain to it. The limit of the number of field value pairs in a record is in the tens of millions.
There is only a limited fixed format for a record (pre-allocated fields). Almost any number of fields can appear almost any number of times in almost any order. Each record is automatically assigned a unique internal record number that is used by the system to build index entries for the record.
The Concept of a Model 204 Record
Base Records
Extension Records
The Structure of a Model 204 Record
Extension Pointer
Data
If there are any preallocated fields in a file (see the OCCURS attribute) every record in that file will begin with the set of such fields. The set of fields is stored in the Record Map in Table D.
After that, in either the order they were ADDed (which always adds the entity at the end of the record), or positioned by an INSERT statement, come a series of field value pairs, repeating field groups and / or pointers to large objects.
Each of the four is described below: