Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 326883 - UpdateNull*Tests fail on MaxDB with "SAP DBTech JDBC: Cannot put ASCII data into this LONG column."
Summary: UpdateNull*Tests fail on MaxDB with "SAP DBTech JDBC: Cannot put ASCII data i...
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: maxdb
Keywords:
Depends on:
Blocks: 284657
  Show dependency tree
 
Reported: 2010-10-04 02:23 EDT by Adrian Goerler CLA
Modified: 2022-06-09 10:10 EDT (History)
3 users (show)

See Also:

Attachments
fix for this issue (1.12 KB, patch)
2010-10-04 07:09 EDT, Adrian Goerler CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian Goerler CLA 2010-10-04 02:23:55 EDT 
On MaxDB, the following CORE LRG tests fail with the message "SAP DBTech JDBC: Cannot put ASCII data into this LONG column.": 

UpdateNullOneToOneValueTest (AllFieldsLockingPolicy)
UpdateNullOneToOneValueTest (SelectedFieldsLockingPolicy)
UpdateNullOneToOneValueTest (AllFieldsLockingPolicy)
UpdateNullOneToOneValueTest (ChangedFieldsLockingPolicy)
UpdateNullOneToOneValueTest (AllFieldsLockingPolicy)
UpdateNullOneToOneValueTest (VersionLockingPolicy)
UpdateNullOneToOneValueTest (TimestampLockingPolicy)
UpdateNullAggregateValueTest (AllFieldsLockingPolicy)
UpdateNullAggregateValueTest (SelectedFieldsLockingPolicy)
UpdateNullAggregateValueTest (ChangedFieldsLockingPolicy)
UpdateNullAggregateValueTest (VersionLockingPolicy)
UpdateNullAggregateValueTest (TimestampLockingPolicy)
UpdateNullOneToManyValueTest (AllFieldsLockingPolicy)
UpdateNullOneToManyValueTest (SelectedFieldsLockingPolicy)
UpdateNullOneToManyValueTest (ChangedFieldsLockingPolicy)
UpdateNullOneToManyValueTest (VersionLockingPolicy)
UpdateNullOneToManyValueTest (TimestampLockingPolicy)
UpdateNullTransformationValueTest (AllFieldsLockingPolicy)
UpdateNullTransformationValueTest (SelectedFieldsLockingPolicy)
UpdateNullTransformationValueTest (ChangedFieldsLockingPolicy)
UpdateNullTransformationValueTest (VersionLockingPolicy)
UpdateNullTransformationValueTest (TimestampLockingPolicy)
UpdateNullManyToManyValueTest (AllFieldsLockingPolicy)
UpdateNullManyToManyValueTest (SelectedFieldsLockingPolicy)
UpdateNullManyToManyValueTest (ChangedFieldsLockingPolicy)
UpdateNullManyToManyValueTest (VersionLockingPolicy)
UpdateNullManyToManyValueTest (TimestampLockingPolicy)
Comment 1 Adrian Goerler CLA 2010-10-04 07:09:54 EDT 
Created attachment 180150 [details]
fix for this issue

In the MaxDB platform, CHAR was mapped as LONG BYTE, which is a LOB on MaxDB. With this fix, only CHAR BYTE is mapped as LONG BYTE.
Comment 2 Adrian Goerler CLA 2010-10-04 07:11:30 EDT 
Tested on MaxDB -> fixes the issue
Checked in at # 8295
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:10:04 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink