You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Kevin Sutter (JIRA)" <ji...@apache.org> on 2007/07/31 20:58:56 UTC
[jira] Closed: (OPENJPA-77) Problems in default setting in
DB2Dictionary , also missing support for DB2 z/OS platforms
[ https://issues.apache.org/jira/browse/OPENJPA-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Sutter closed OPENJPA-77.
-------------------------------
> Problems in default setting in DB2Dictionary , also missing support for DB2 z/OS platforms
> ------------------------------------------------------------------------------------------
>
> Key: OPENJPA-77
> URL: https://issues.apache.org/jira/browse/OPENJPA-77
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Reporter: Catalina Wei
> Assignee: Kevin Sutter
> Fix For: 0.9.7
>
>
> There are following problems:
> 1. the default storeCharsAsNumbers = true, does not work well in DB2. Preferable default setting should be false.
> 2. nextSequenceSQL() generates DB2 UDB specific SQLs which fails on DB2 z/OS platforms.
> 3. lastGeneratedKeyQuery SQL string is applicable for DB2 UDB only, needs to provide DB2 z/OS specific SQL.
> 4. bigintTypeName ="BIGINT" does not work for DB2 z/OS Version 8.
> 5. characterColumnSize = 255 for default CHAR or VARCHAR fails on DB2 UDB platforms. DB2 UDB CHARACTER size limit is 254
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.