Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <4218141.141501292440683955.JavaMail.jira@thor>
Date: Wed, 15 Dec 2010 14:18:03 -0500 (EST)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4614) JDBC metadata gives incorrect lengths
 for timestamps
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Knut Anders Hatlen updated DERBY-4614:
--------------------------------------

    Affects Version/s:     (was: 10.7.1.2)
                           (was: 10.8.0.0)
                       10.7.1.1
        Fix Version/s: 10.7.1.2

> 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.2, 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
>
>
> 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.