Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <4505259.98251291403590751.JavaMail.jira@thor>
Date: Fri, 3 Dec 2010 14:13:10 -0500 (EST)
From: "Rick Hillegas (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 ]

Rick Hillegas updated DERBY-4614:
---------------------------------

    Attachment: derby-4614-01-ad-warmedUp.diff

Attaching a new rev of the patch, derby-4614-01-ad-warmedUp.diff. DatabaseMetaDataTest failed on the last rev when run on Java 5. The new rev fixes the reflection performed by that test when it invokes the getFunctionColumns() method. Now DatabaseMetaDataTest runs cleanly on Java 5. Re-running regression tests now.

Touches the same files as the previous 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-01-ac-warmedUp.diff, derby-4614-01-ad-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.