Community
Participate
Working Groups
related to bug #359130 The following table DDL: CREATE TABLE SECONDARY ( EMPNO NUMERIC(4), ENAME VARCHAR(10), JOB VARCHAR(9), MGR NUMERIC(4), HIREDATE DATE, SAL DECIMAL(7,2), COMM DECIMAL(7,2), DEPTNO NUMERIC(2), PRIMARY KEY (EMPNO) ) uses Oracle's DATE column type for the field HIREDATE. Unlike other DB platform, Oracle's DATE type includes time information as well. In the static helper methods org.eclipse.persistence.tools.dbws.Util>getXMLTypeFromJDBCType org.eclipse.persistence.tools.dbws.Util>getJDBCTypeFromTypeName DATE is mapped to java.sql.Date and {xsd}date - for Oracle platform we need to override this 'natural' mapping to use Timestamp so that Oracle DATA column information is not lost
Upon further research, the information leading up to entering this bug is wrong: Oracle's DATE datatype does NOT hold information beyond the second precision: use of java.sql.Data and xsd:date is correct.
closed
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink