/mcpThis is a variable length string. The maximum length will be specified in bytes. The database stores string data using UTF-8 encoding. Refer to the Validation for limitations on characters and length of strings. 2.3 Table Level Rules and Field Details Unless otherwise indicated, all tables and data are replicated throughout the cluster. Note for developers The Data Dictionary source is the same set of CSV files used to create the database. Each table, field, rule, and constraint has an ID next to it (in parentheses) that indicates the source. The codes are always <type>-number. The type codes are as follows: TI Table Information from TypeTableInfo.csv FI Field Information from TypeFieldInfo.csv RFI Related Field Information from TypeRelatedFieldInfo.csv MFI Mulit-Field Index from TypeMultiFieldIndex.csv RI Rule Information from TypeRuleInfo.csv For example, RFI-21 is Related Field Info for enum = 21 in TypeRelatedFieldInfo.csv. Error messages from business rule violations have two components - Error code and SQL Exception. For example, Error: java.sql.SQLException: 37131, SQL State: IX000, Error Code: -746. Error Code -746 indicates an exception based on database rules. If specific error message text is not displayed, it can be found in TypeDbErrors table where SQLException value is the value in the enum column. SQLException values above 25,000 also correlate directly to data dictionary entries at follows: Errors occurring because of validation or check constraints defined in TypeRelatedFieldInfo have a number that is equal to 25,000 plus the related field info rule number in datadicationary. For example, if an error 25142 occurs while updating ApplicationDialRule table, you can find the associated constraint with 25142-25000 = (RFI-)142. Check the constraints below the field definitions in the table (or just search this document for "RFI-142"). •
