[ http://issues.apache.org/jira/browse/DERBY-194?page=comments#action_62135 ] Myrna van Lunteren commented on DERBY-194: ------------------------------------------
When this get fixed, the PRECISION field of Metadata.getTypeInfo should also be changed to match. > getPrecision() on TIME and TIMESTAMP is zero > -------------------------------------------- > > Key: DERBY-194 > URL: http://issues.apache.org/jira/browse/DERBY-194 > Project: Derby > Type: Bug > Components: JDBC > Versions: 10.0.2.0 > Environment: Windows XP SP1 Professional > Reporter: George Baklarz > Priority: Minor > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
