| Summary: | hundreds jpa oracle specific TimeStamp related WriteTypeObjectTests failed on oracle 10.2.0.4 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Yiping Zhao <yiping.zhao> | ||||
| Component: | Eclipselink | Assignee: | Andrei Ilitchev <andrei.ilitchev> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | andrei.ilitchev, eclipselink.orm-inbox | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Yiping Zhao
Created attachment 177961 [details] suggested patch. This is a test issue. In bug 323420 I simplified in TIMESTAMPTester verification check for calToTSLTZ (calendar written into TIMESTAMPTZ, then read back should be the same). That worked when Timestamp obtained from TIMESTAMPTZ is in GMT (11.1.0.7 and later); but didn't work otherwise. Now the test checks isTimestampInGmt and uses the new approach if it is, and the old approach otherwise. Checked the patch into trunk, 2.1.2 is pending. Checked the patch into 2.1.2. The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |