[ http://issues.apache.org/jira/browse/DERBY-194?page=comments#action_12312570 ]
A B commented on DERBY-194: --------------------------- Patch was committed with svn revision 179839. I tried to "Resolve" this issue with a comment, but something went wrong with JIRA so I don't think it went through. That said, the "resolve" option is no longer available, so I guess "close" is the next option. SO, George Baklarz, if you can do an "svn update" and then confirm that the problem has been fixed, please post saying so and I will close this issue...Thanks. > 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 > Assignee: A B > Priority: Minor > Fix For: 10.1.0.0 > Attachments: derby-194.patch, derby-194.stat > > 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
