[
https://issues.apache.org/jira/browse/DERBY-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905467#action_12905467
]
Knut Anders Hatlen commented on DERBY-4614:
-------------------------------------------
Hi Nirmal,
It looks to me that this issue and DERBY-4625 are orthogonal issues that would
be better addressed separately. What are the problems you have found that made
them difficult to separate? To me it looks like the changes in
SQLTimestamp.java and DateTimeTest.java are only related to DERBY-4625, and the
changes in the other files are only related to this issue. Would that be a
reasonable way to split the patch?
> 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
>
>
> 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.
