[
https://issues.apache.org/jira/browse/DERBY-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905533#action_12905533
]
C.S. Nirmal J. Fernando commented on DERBY-4614:
------------------------------------------------
Hi Knut,
Regarding your second comment,
1) I found that in java/engine/org/apache/derby/iapi/types/TypeId.java we use
"public static final int TIMESTAMP_MAXWIDTH =
DRDAConstants.DRDA_TIMESTAMP_LENGTH; // yyyy-mm-dd hh:mm:ss.fffffffff".
2) I'll look into it.
3) I'll add some tests.
Regarding your third comment,
Sorry about that I did not run derbyall previously, I'll update those tests
soon, thanks for running tests Knut!
Thanks again for quick reviews!
> 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.
