[
https://issues.apache.org/jira/browse/DERBY-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905514#action_12905514
]
Kathey Marsden commented on DERBY-4614:
---------------------------------------
Hi Nirmal,
I haven't had a chance to look at the patch, but i know earlier you asked
about specific tests for database metadata. Traditionally one area of concern
regrarding these queries has been upgrade because they are stored in the
database. Hopefully we have that worked out with the fix for DERBY-1107,
I believe the upgrade tests test test metadata make sure that everything
behaves properly. But it would be interesting to do some ad hoc testing around
soft upgrade, particularly with maintenance versions around your changes.
Thanks
Kathey
> 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.
