[
https://issues.apache.org/jira/browse/DERBY-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-4614:
---------------------------------
Attachment: derby-4614-01-ab-warmedUp.diff
Attaching derby-4614-01-ab-warmedUp.diff. This removes the special case in
ColumnMetaData.getScale() per Knut's second recommendation on 2010-09-02. Tests
ran cleanly for me.
Touches the same files as the previous version of the warmed-up 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
> Attachments: derby-4614-01-aa-warmedUp.diff,
> derby-4614-01-ab-warmedUp.diff, derby-4614-1.diff, derby-4614-fs.html,
> derby_4614-2.diff
>
>
> 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.
