Internal Representation of INTERVAL MINUTE TO SECOND
Conceptually, INTERVAL MINUTE TO SECOND is treated as a record composed of the following fields.
Field Name | Storage Format | Total Length |
---|---|---|
MINUTE | SMALLINT | 6 bytes |
SECOND | INTEGER |
External Representation of INTERVAL MINUTE TO SECOND
INTERVAL MINUTE TO SECOND types are imported and exported in record and indicator modes as CHARACTER data using the client character set.
WHEN fractional_seconds_precision is … | THEN the type and format are … |
---|---|
0 | Type: CHARACTER(precision + 4) |
Format: '-m(precision):ss' | |
n where n is 1 - 6 |
Type: CHARACTER(precision + n + 5) |
Format: '-m(precision):ss.s(n)' |
For example, for INTERVAL MINUTE(2) TO SECOND(0), the value might be something like ‘ 17:39’.
Range of Values
The range of values for INTERVAL MINUTE TO SECOND is as follows.
Type, Precision, and Fractional Seconds Precision | Minimum Value | Maximum Value |
---|---|---|
INTERVAL MINUTE(1) TO SECOND(0) | -'9:59' | '9:59' |
INTERVAL MINUTE(1) TO SECOND(1) | -'9:59.9' | '9:59.9' |
INTERVAL MINUTE(1) TO SECOND(2) | -'9:59.99' | '9:59.99' |
INTERVAL MINUTE(1) TO SECOND(3) | -'9:59.999' | '9:59.999' |
INTERVAL MINUTE(1) TO SECOND(4) | -'9:59.9999' | '9:59.9999' |
INTERVAL MINUTE(1) TO SECOND(5) | -'9:59.99999' | '9:59.99999' |
INTERVAL MINUTE(1) TO SECOND(6) | -'9:59.999999' | '9:59.999999' |
INTERVAL MINUTE(2) TO SECOND(0) | -'99:59' | '99:59' |
INTERVAL MINUTE(2) TO SECOND(1) | -'99:59.9' | '99:59.9' |
INTERVAL MINUTE(2) TO SECOND(2) | -'99:59.99' | '99:59.99' |
INTERVAL MINUTE(2) TO SECOND(3) | -'99:59.999' | '99:59.999' |
INTERVAL MINUTE(2) TO SECOND(4) | -'99:59.9999' | '99:59.9999' |
INTERVAL MINUTE(2) TO SECOND(5) | -'99:59.99999' | '99:59.99999' |
INTERVAL MINUTE(2) TO SECOND(6) | -'99:59.999999' | '99:59.999999' |
INTERVAL MINUTE(3) TO SECOND(0) | -'999:59' | '999:59' |
INTERVAL MINUTE(3) TO SECOND(1) | -'999:59.9' | '999:59.9' |
INTERVAL MINUTE(3) TO SECOND(2) | -'999:59.99' | '999:59.99' |
INTERVAL MINUTE(3) TO SECOND(3) | -'999:59.999' | '999:59.999' |
INTERVAL MINUTE(3) TO SECOND(4) | -'999:59.9999' | '999:59.9999' |
INTERVAL MINUTE(3) TO SECOND(5) | -'999:59.99999' | '999:59.99999' |
INTERVAL MINUTE(3) TO SECOND(6) | -'999:59.999999' | '999:59.999999' |
INTERVAL MINUTE(4) TO SECOND(0) | -'9999:59' | '9999:59' |
INTERVAL MINUTE(4) TO SECOND(1) | -'9999:59.9' | '9999:59.9' |
INTERVAL MINUTE(4) TO SECOND(2) | -'9999:59.99' | '9999:59.99' |
INTERVAL MINUTE(4) TO SECOND(3) | -'9999:59.999' | '9999:59.999' |
INTERVAL MINUTE(4) TO SECOND(4) | -'9999:59.9999' | '9999:59.9999' |
INTERVAL MINUTE(4) TO SECOND(5) | -'9999:59.99999' | '9999:59.99999' |
INTERVAL MINUTE(4) TO SECOND(6) | -'9999:59.999999' | '9999:59.999999' |
Implicit and Explicit INTERVAL MINUTE TO SECOND Conversion
Vantage performs implicit conversion from one Interval data type to another Interval type in some cases. You can also use CAST to explicitly convert one Interval type to another.
Conversions are possible only within the same INTERVAL family. For example, you may convert a YEAR interval to months, but not to days or hours.
For more information, see Teradata Vantage™ - SQL Functions, Expressions, and Predicates, B035-1145.