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 "C.S. Nirmal J. Fernando (JIRA)" <ji...@apache.org> on 2010/08/29 13:31:53 UTC
[jira] Commented: (DERBY-4614) JDBC metadata gives incorrect
lengths for timestamps
[ https://issues.apache.org/jira/browse/DERBY-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903957#action_12903957 ]
C.S. Nirmal J. Fernando commented on DERBY-4614:
------------------------------------------------
Hi Rick,
I would like to take up this bug. I've read through the specification that you've attached.
Can you suggest me an entry point to implement the spec? I can see that solving this bug,
will help to solve the other linked bugs.
Thanks.
> JDBC metadata gives incorrect lengths for timestamps
> ----------------------------------------------------
>
> Key: DERBY-4614
> URL: https://issues.apache.org/jira/browse/DERBY-4614
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.6.1.0
> Reporter: Rick Hillegas
> Attachments: derby-4614-fs.html
>
>
> While looking into DERBY-2602, I noticed that Derby gives the wrong lengths for various fields in the JDBC metadata for timestamps. I will attach a spec describing what I think should be done to correct this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.