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

OpenJPA

Problems in default setting in DB2Dictionary , also missing support for DB2 z/OS platforms

Created: 09/Nov/06 05:55 PM Updated: 31/Jul/07 06:58 PM

Return to search

Component/s:

jdbc

Affects Version/s:

None

Fix Version/s:

0.9.7

Time Tracking:

Not Specified

Resolution Date:

29/Dec/06 03:23 PM

Description

« Hide

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

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

[ Permlink | « Hide ]

Kevin Sutter added a comment - 29/Dec/06 03:15 PM

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.

[ Permlink | « Hide ]

Kevin Sutter added a comment - 29/Dec/06 03:23 PM

Catalina provided a patch to me to check out. The changes looked good and the regression bucket ran just fine. The z/OS specific testing was done by another team.