| Summary: | UpdateNull*Tests fail on MaxDB with "SAP DBTech JDBC: Cannot put ASCII data into this LONG column." | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Adrian Goerler <adrian.goerler> | ||||
| Component: | Eclipselink | Assignee: | Project Inbox <eclipselink.incubator-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | andreas.fischbach, krum.tsvetkov, sabine.heider | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | maxdb | ||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 284657 | ||||||
| Attachments: |
|
||||||
|
Description
Adrian Goerler
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.
Tested on MaxDB -> fixes the issue Checked in at # 8295 The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |