[#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:

David Wisneski made changes - 09/Nov/06 07:31 PM

Field	Original Value	New Value
Assignee		David Wisneski [ wisneskid ]

David Wisneski made changes - 09/Nov/06 07:42 PM

Attachment

OPENJPA-77.openjpa-jdbc.patch.txt [ 12344708 ]

David Wisneski made changes - 10/Nov/06 12:02 AM

Status

Open [ 1 ]

In Progress [ 3 ]

Kevin Sutter made changes - 29/Dec/06 03:23 PM

Assignee	David Wisneski [ wisneskid ]	Kevin Sutter [ kwsutter ]
Resolution		Fixed [ 1 ]
Status	In Progress [ 3 ]	Resolved [ 5 ]

David Wisneski made changes - 29/Dec/06 07:25 PM

Attachment

~~OPENJPA-77~~.openjpa-jdbc.patch.txt [ 12344708 ]

Patrick Linskey made changes - 01/Mar/07 02:13 AM

Fix Version/s

0.9.7 [ 12312340 ]

Kevin Sutter made changes - 31/Jul/07 06:58 PM

Status

Resolved [ 5 ]

Closed [ 6 ]