Issue Details (XML | Word | Printable)

Key: HB-545
Type: Improvement Improvement
Status: Closed Closed
Resolution: Rejected
Priority: Minor Minor
Assignee: Unassigned
Reporter: Martin Priekopa
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
z - Hibernate 2

oracle 9 dialect - change of timestamp mapping

Created: 12/Dec/03 07:19 AM   Updated: 07/Jul/04 12:15 AM   Resolved: 07/Mar/04 05:23 AM
Return to search
Component/s: core
Affects Version/s: 2.1 final
Fix Version/s: 2.1.3

Time Tracking:
Not Specified

Environment: all hibernate versions, oracle 9 DB
Issue Links:
Relates

Participants: CVS Notification Service, Jonas Kilian, Lutz Zimmermann, Martin Priekopa and Max Rydahl Andersen


 Description  « Hide

What about to change mapping of hibernate timestamp from oracle's DATE datatype to TIMESTAMP datatype.



Max Rydahl Andersen added a comment - 17/Jan/04 06:12 PM

why ?


Jonas Kilian added a comment - 02/May/04 09:45 AM

Oracle's DATE datatype does NOT support milliseconds whereas java.sql.Timestamp DOES! see:
http://www.databasejournal.com/features/oracle/article.php/2234501

excerpt:

"...One of the main problems with the DATE datatype was its' inability to be granular enough to determine which event might have happened first in relation to another event. Oracle has expanded on the DATE datatype and has given us the TIMESTAMP datatype which stores all the information that the DATE datatype stores, but also includes fractional seconds..."


Lutz Zimmermann added a comment - 25/Jun/04 03:18 PM

Bug was not fixed in release >=2.1.3


Lutz Zimmermann added a comment - 25/Jun/04 03:19 PM

Was declared fixed, but isn't.


CVS Notification Service added a comment - 07/Jul/04 12:15 AM

CVS COMMIT LOG:
SUBJECT: [Hibernate-commits] Hibernate3/src/org/hibernate/dialect Oracle9Dialect.java,1.2,1.3
fix HB-545, use Oracle TIMESTAMP type