Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Unit test failures due to date/time precision mismatches
Description
FooBarTest#testQuery is failing because a Oracle DATE values include time up to seconds. This method executes the following:
{{list = s.createQuery( "from Foo foo where ? = some elements(foo.component.importantDates)" ) .setParameter( 0, new Date(), StandardBasicTypes.DATE ) .list();
Unless the value is within a half second of what was persisted, no results will be returned and the test will fail.
The test will pass if foo.getTimestamp() is bound instead. This is because Foo#onSave initializes the timestamp property to the current time, and the same value is ultimately added to {{Foo.component.importantDates.
Activity
Show:
Former userDecember 2, 2015 at 11:09 PM
Fixed in master and 5.0 branches.
Former userNovember 25, 2015 at 1:49 AM
org.hibernate.test.temporal.TimePropertyTest fails using MariaDB because the precision of a java.util.Date value in memory is greater than the persisted TIME value.
FooBarTest#testQueryis failing because a Oracle DATE values include time up to seconds.This method executes the following:
{{list = s.createQuery( "from Foo foo where ? = some elements(foo.component.importantDates)" )
.setParameter( 0, new Date(), StandardBasicTypes.DATE )
.list();
Unless the value is within a half second of what was persisted, no results will be returned and the test will fail.
The test will pass if
foo.getTimestamp()is bound instead. This is becauseFoo#onSave initializes the timestamp property to the current time, and the same value is ultimately added to {{Foo.component.importantDates.