You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2011/03/01 18:40:37 UTC
[jira] Updated: (DERBY-4614) JDBC metadata gives incorrect lengths
for timestamps
[ https://issues.apache.org/jira/browse/DERBY-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-4614:
---------------------------------
Attachment: releaseNote.html
Adjusted the release note.
> 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.7.1.1
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Fix For: 10.7.1.3, 10.8.0.0
>
> Attachments: d4614_hang.java, derby-4614-01-aa-warmedUp.diff, derby-4614-01-ab-warmedUp.diff, derby-4614-01-ac-warmedUp.diff, derby-4614-01-ad-warmedUp.diff, derby-4614-01-ae-warmedUp.diff, derby-4614-02-ab-compatProblem.diff, derby-4614-1.diff, derby-4614-fs.html, derby_4614-2.diff, releaseNote.html, releaseNote.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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira