[
https://issues.apache.org/jira/browse/DERBY-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971325#action_12971325
]
Rick Hillegas commented on DERBY-4614:
--------------------------------------
Tests ran cleanly for me. Committed derby-4614-02-ab-compatProblem.diff at
subversion revision 1049180.
> 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.7.1.2, 10.8.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: d4614_hang.java, derby-4614-01-aa-warmedUp.diff,
> derby-4614-01-ab-warmedUp.diff, derby-4614-01-ac-warmedUp.diff,
> derby-4614-01-ad-warmedUp.diff, derby-4614-01-ae-warmedUp.diff,
> derby-4614-02-ab-compatProblem.diff, derby-4614-1.diff, derby-4614-fs.html,
> derby_4614-2.diff, releaseNote.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.
