[DERBY-194] getPrecision() on TIME and TIMESTAMP is zero

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.0.2.0
• Fix Version/s: 10.1.1.0
• Component/s: JDBC
• Environment: Windows XP SP1 Professional
• Assignee: A B
• Reporter: George Baklarz
• Created: 04/Apr/05 08:15
• Updated: 08/Jun/05 08:03
• Resolved: 04/Jun/05 15:51

Description

Sun JDBC defines getPrecision() to return either the maximum length or maximum number of digits of the column, or zero for failure (such as the precision is unknown).

http://docs.sun.com/source/816-6105-10/apicola.htm#211083

The DATE field returns 10 characters on a getPrecision() call so why doesn't TIME and TIMESTAMP give a precision length equal to the display length? Just seems inconsistent that DATE would return a precision (as well as all other data types) and not TIME nor TIMESTAMP.