rs_formats
The following table lists the columns for the rs_formats view. The equivalent jcs_formats view is available for backward compatibility reasons. The difference between the two is the data type of the date/time columns; the rs_* views use TIMESTAMP WITH TIME ZONE while the jcs_* views use DATE.
| Column | Datatype | Description |
| ID | NUMBER | The unique id of a format |
| PARTITION | VARCHAR2 | The unique partition of a format |
| NAME | VARCHAR2 | The unique name of a format |
| VERSION | NUMBER | The version number of a format |
| DESCRIPTION | VARCHAR2 | The description of a format |
| APPLICATION_PARTITION | VARCHAR2 | The partition of the application; can be used to group Redwood objects in logical groups |
| APPLICATION_NAME | VARCHAR2 | The name of the application; can be used to group Redwood objects in logical groups |
| EXTENSION | VARCHAR2 | The case-sensitive extension used in the output filename |
| TYPE | VARCHAR2 | The type of data (ASCII or BINARY) |
| OUTPUT_INDEX_TYPE | VARCHAR2 | If the outputfile is to be indexed and if so through which filter |
| LOG_INDEX_TYPE | VARCHAR2 | If the logfile is to be indexed and if so through which filter |
| MIMETYPE | VARCHAR2 | The mimetype belonging to this format |
| COMMENT_TEXT | VARCHAR2 | Comment describing the format |
| CHARACTER_SET | VARCHAR2 | The characterset belonging to this format |
note
VERSION: Version is not increased with one anymore after changing the object.
note
OUTPUT_INDEX_TYPE: Version 9 does have Full text search anymore. Therefore this column is always empty.
note
LOG_INDEX_TYPE: Version 9 does have Full text search anymore. Therefore this column is always empty.
note
CHARACTER_SET: In version 9 it is not possible to define a character set. Therefore this column is always empty.
plsqlTopic
onsiteTopic