You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Fay Wang (JIRA)" <ji...@apache.org> on 2010/06/02 21:24:48 UTC
[jira] Created: (OPENJPA-1679) Index name too long for DB2 zOS when
schema is present
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.
[jira] Commented: (OPENJPA-1679) Index name too long for DB2 zOS
when schema is present
Posted by "Fay Wang (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (OPENJPA-1679) Index name too long for DB2 zOS
when schema is present
Posted by "Fay Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fay Wang resolved OPENJPA-1679.
-------------------------------
Resolution: Fixed
> 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.
[jira] Closed: (OPENJPA-1679) Index name too long for DB2 zOS when
schema is present
Posted by "Fay Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fay Wang closed OPENJPA-1679.
-----------------------------
> 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.