db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (DERBY-4614) JDBC metadata gives incorrect lengths for timestamps
Date Thu, 09 Dec 2010 10:44:00 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen reopened DERBY-4614:
---------------------------------------

      Assignee: Rick Hillegas

I'm reopening this issue since the compatibility tests have not been able to complete in the
tinderbox or in the nightly tests after the patch was checked in. They seem to hang when testing
old clients against servers running trunk.

> 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.2, 10.8.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: 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-1.diff, derby-4614-fs.html, derby_4614-2.diff, 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message