[
https://issues.apache.org/jira/browse/DERBY-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910546#action_12910546
]
C.S. Nirmal J. Fernando commented on DERBY-4614:
------------------------------------------------
Hi,
I've separated the derby-4625 issue related changes from this issue, in patch
#2.
But I couldn't find any time to look at Knut's 2) & 3) points in his one before
last comment.
I've unassigned my self from this issue since I've to concentrate on my final
year research project.
Things to be done:
1) Run regression tests on new patch
2) Consider Knut's above mentioned 2nd & 3rd points
Thanks for all the help provided on this issue!
> 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
> Assignee: C.S. Nirmal J. Fernando
> Attachments: derby-4614-1.diff, derby-4614-fs.html, derby_4614-2.diff
>
>
> 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.
