[#HB-1049] Oracl9i-Dialect translates to DATE, should be TIMESTAMP

Hibernate2

Oracl9i-Dialect translates to DATE, should be TIMESTAMP

Created: 25/Jun/04 03:18 PM Updated: 20/Sep/04 03:17 AM

Component/s:

core

Affects Version/s:

2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4

Fix Version/s:

3.0 alpha

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

File Attachments:

Oracle9Dialect.patch (0.8 kb)

Environment:

We are using realase Hibernate-2.1.4

Issue Links:

Relates

This issue relates to:
	~~HB-545~~ oracle 9 dialect - change of timestam...

This issue relates to:
	~~HB-545~~ oracle 9 dialect - change of timestam...

Description

« Hide

Bug was already reported and declared fixed in 2.1.3, but Oracle9iDialect.java still maps Type.TIMESTAMP to DATE. It should be TIMESTAMP, because of its greater precision.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Lutz Zimmermann - [25/Jun/04 03:18 PM ]

Bug was not fixed in release >=2.1.3

[ Permlink | « Hide ]

Lutz Zimmermann - [25/Jun/04 03:19 PM ]

Was declared fixed, but isn't.

[ Permlink | « Hide ]

Lutz Zimmermann - [25/Jun/04 04:08 PM ]

This patch changes mapping for Types.TIMESTAMP from DATE to TIMESTAMP

[ Permlink | « Hide ]

Gavin King - [26/Jun/04 09:44 AM ]

Fixed in Hibernate3 branch (not in Hibernate 2.1, since it could potentially break existing stuff).

[ Permlink | « Hide ]

Lutz Zimmermann - [26/Jun/04 10:12 AM ]

Thanks Gavin, didn't think about that.
But really gave me good insight on Hibernate's "bowels" and my Colleagues Tefan & Methin some cosy hours in our customer's office (lights were out due to cost-containment) ;-)

[ Permlink | « Hide ]

Raimund - [13/Aug/04 11:41 AM ]

>> Gavin wrote: not in Hibernate 2.1, since it could potentially break existing stuff

Gavin, would you please elaborate on the "stuff" it could break? Is the workaround to simply define your Oracle columns as timestamp versus changing Oracle9Dialect.java?

[ Permlink | « Hide ]

Gavin King - [13/Aug/04 06:08 PM ]

You can always customize the generated DDL by using <column sql-type="TIMESTAMP"/>.

I mean, it will change people's existing Oracle schemas, which is unacceptable in a point release.

[ Permlink | « Hide ]

redmark - [20/Sep/04 03:17 AM ]

i can use custom column in property, but i can't do it version because version has not <column> tag