Extending the data type file

You can extend the data type XML file.

About this task

To extend the data type XML file:

Procedure

  1. Create a new <runtime_sandbox>/extensions/global/etc/datatypes.xml file, if it does not already exist.

    If the /global/etc/ directory structure does not exist, create the required directory structure.

    Note: When datatypes are extended through <runtime_sandbox>/extensions/global/etc/datatypes.xml file, the resources.jar file needs to be rebuilt before running the dbverify tool.
  2. Add an XML root node in the same way it appears in the <runtime_sandbox>/repository/datatypes/datatypes.xml file.
  3. Add any differential values for the datatypes, including the following:
    • Add and define parameters for new datatypes
    • Modify parameters of existing datatypes
    Note: For existing datatypes, you can modify only the UI related attributes in the datatypes.xml file such as UI Size and UITableSize.
    Note: You cannot resize the Date input fields within the console across the board even if your date format is larger than the default date format used by the application.
    Note: The application reserves the Type attribute for internal use, and so you cannot override it. All other attributes can be overridden.
    Note: For existing datatypes, you cannot change a character type to a numeric type. For example, you cannot change a CHAR type to NUMBER type. An exception will be thrown for such invalid conversions. Following conversions are treated as invalid conversions:
    • Converting NVARCHAR, NCHAR, VARCHAR2, BLOB, CLOB, TIME, DATE, DATETIME type to NUMBER type.
    • Converting NVARCHAR, NCHAR, VARCHAR2, BLOB, CLOB, TIME, DATE, DATETIME type to SCI_LONG type.
    • Converting NVARCHAR, NCHAR, VARCHAR2, BLOB, CLOB, TIME, DATE, DATETIME type to SCI_INT type.
    • Converting any type to BLOB, CLOB type.
    • Converting BLOB, CLOB type to any type.
    • Converting from any type to DATE, DATETIME, TIME type.
    Note: The invalid conversions are not specific to any database. The invalid conversions are based on the criteria whether the new datatype can hold the data that the old datatype column can take.

  4. Build and deploy your extensions.