OracleDialect incorrectly maps timestamps and dates to Hibernate Date Type

Description

OracleDialect maps an jdbc timestamp type to a hibernate date type, and maps by default, jdbc date type to hibernate org.hibernate.type.DateType. Hibernate Date Type translation uses ResultSet.getDate which means that time is truncated from the date. This is not what you want, you want to include the time. These should use a hibernate TypeStampType. This is what a java.util.Date mapping uses. Right now, you will get different results if running an sql query on the same table vs. a hibernate hql query, it will map to different types. Propose the OracleDialect class do this:

registerColumnType( Types.DATE, Hibernate.TIMESTAMP.getName() );
registerColumnType( Types.TIMESTAMP, Hibernate.TIMESTAMP.getName() );

Environment

org.hibernate.dialect.OracleDialect

Activity

Show:
Brett Meyer
April 7, 2014, 5:42 PM

In an effort to clean up, in bulk, tickets that are most likely out of date, we're transitioning all ORM 3 tickets to an "Awaiting Test Case" state. Please see http://in.relation.to/Bloggers/HibernateORMJIRAPoliciesAndCleanUpTactics for more information.

If this is still a legitimate bug in ORM 4, please provide either a test case that reproduces it or enough detail (entities, mappings, snippets, etc.) to show that it still fails on 4. If nothing is received within 3 months or so, we'll be automatically closing them.

Thank you!

Brett Meyer
July 8, 2014, 3:11 PM

Bulk rejecting stale issues. If this is still a legitimate issue on ORM 4, feel free to comment and attach a test case. I'll address responses case-by-case. Thanks!

Rejected

Assignee

Unassigned

Reporter

BT

Fix versions

None

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Affects versions

Priority

Major
Configure