You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "A B (JIRA)" <de...@db.apache.org> on 2005/05/26 23:31:54 UTC

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

     [ http://issues.apache.org/jira/browse/DERBY-194?page=all ]

A B reassigned DERBY-194:
-------------------------

    Assign To: A B

> 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

>
> 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