[OPENJPA-77] Problems in default setting in DB2Dictionary , also missing support for DB2 z/OS platforms

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.9.7
• Component/s: jdbc
• Assignee: Kevin W. Sutter
• Reporter: Catalina Wei
• Created: 09/Nov/06 17:55
• Updated: 31/Jul/07 18:58
• Resolved: 29/Dec/06 15:23

Description

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