http://issues.apache.org/jira/browse/OPENJPA-77?page=comments#action_12461393 ] 
Kevin Sutter commented on OPENJPA-77:

Catalina has provided a new private patch for this Issue which does not 
introduce the multiple database dictionaries for the various DB2 z/OS versions. 
 It's much cleaner.  I'm in the process of verifying it and will be committing 
the changes soon.  Thanks. 

> Problems in default setting in DB2Dictionary , also missing support for DB2 
> z/OS platforms
> ------------------------------------------------------------------------------------------
>                 Key: OPENJPA-77
>                 URL: http://issues.apache.org/jira/browse/OPENJPA-77
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>            Reporter: Catalina Wei
>         Assigned To: David Wisneski
>         Attachments: OPENJPA-77.openjpa-jdbc.patch.txt
> 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.
If you think it was sent incorrectly contact one of the administrators: 
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to