Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Column data can have an associated data dictionary file generated. An example of a generated file name for a dictionary file for a table that has the identifier "Table1" and a column that has the identifier "Label" is 4.Table1.Label.dictionary. For an explanation of the interpretation of the substrings within the file name, see section 2.2.
The data dictionary contains information that is used to decode the value in the source data that a data identifier represents. The data dictionary file contains an array of unique values that appear in the source data. The file is ordered by data identifier so the first value in the file represents the lowest data identifier, the second value in the file represents the next-lowest data identifier, and so on. Dictionaries that contain only integer or floating point data are not compressed. Dictionaries that contain strings might have parts of the dictionary that are compressed. In the case of dictionaries that contain strings or BLOBs, although most parts of the dictionary file are not compressed, the specific strings or BLOBs might be compressed by using a Huffman compression. BLOBs are pre-encoded by means of base64 encoding and are therefore treated as strings (and stored in a string dictionary). For a discussion of the type of Huffman compression that is used, see section 2.7.
It is necessary to reference the XML metadata file to determine whether a data dictionary file is present for a data column. This metadata is contained in the same file as the column data storage file metadata (see section 2.3.1). If a particular XMRawColumn object—specifically, the XMRawColumn object of the Column item in the Columns collection that has a name equal to the column name—has a DataObject in the DataObjects collection for which the value of the class attribute equals one of the values in the following list, the column MUST have a column data dictionary file generated.
XMHashDataDictionary<XM_Real> (section 2.5.2.19)
XMHashDataDictionary<XM_Long> (section 2.5.2.18)
XMHashDataDictionary<XM_String> (section 2.5.2.22)
For an explanation of how to interpret the XML metadata file see section 2.5.