Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <21649831.141321275506796860.JavaMail.jira@thor>
Date: Wed, 2 Jun 2010 15:26:36 -0400 (EDT)
From: "Fay Wang (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Commented: (OPENJPA-1679) Index name too long for DB2 zOS
 when schema is present
In-Reply-To: <12716006.141251275506688052.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/OPENJPA-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874755#action_12874755 ] 

Fay Wang commented on OPENJPA-1679:
-----------------------------------

Fix is checked in (r-950604) via JIRA-1596 to openjpa 2.0 branch. 

> Index name too long for DB2 zOS when schema is present
> ------------------------------------------------------
>
>                 Key: OPENJPA-1679
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1679
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 2.0.0
>            Reporter: Fay Wang
>            Assignee: Fay Wang
>             Fix For: 2.0.1
>
>
> OPENJPA-1596 has already been marked as fixed in 2.0.0-beta3.  A new JIRA is open for any additional changes in openjpa 2.0.0. Otherwise, the 2.0.1 release notes will not denote that this change was included.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.