[
https://issues.apache.org/jira/browse/DERBY-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904639#action_12904639
]
Rick Hillegas commented on DERBY-4614:
--------------------------------------
Hi Nirmal,
I don't have a comprehensive list of tests which stress the metadata calls so I
would recommend running the full regression test suite. Before doing that,
though, I would recommend running the following tests standalone:
DatabaseMetaDataTest
TestDbMetaData
ParameterMetaDataJdbc30Test
ResultSetMetaDataTest
PrepStmtMetaDataTest
In addition, I would recommend running the upgrade tests because they test the
metadata in old versions of Derby and you will want to make sure that they
don't break when you change the metadata in 10.7.
Thanks,
-Rick
> 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-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.
