[
https://issues.apache.org/jira/browse/DERBY-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903975#action_12903975
]
Bryan Pendleton commented on DERBY-4614:
----------------------------------------
Some good places to start might include:
1) Setting up
java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/ResultSetMiscTest.java
in your debugger, so that you can have an easy way to set breakpoints in various
metadata methods and hit them from the test.
2) Have a look at
java/engine/org/apache/derby/impl/jdbc/EmbedResultSetMetaData.java
and
java/engine/org/apache/derby/iapi/types/DataTypeUtilities.java
to get a feel for how some of the RSMD methods are implemented for embedded
Derby
3) Have a look at
java/client/org/apache/derby/client/am/ColumnMetaData.java
to get a feel for how some of the RSMD methods are implemented for
client/server Derby
Then I'd suggest having a close look through the spec and ensuring that
the existing test programs provide reasonable test coverage for the API calls
of interest.
> 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.
