Comparing hibernate-mapped dates?

How can i map a date from a java object to a database with Hibernate? I try different approaches, but i am not happy with them. Why? Let me explain my issue. I have the following class [1] including the main method i invoke and with the following mapping [2]. The issue about this approach you can see, when you look at the console output.







Thu Oct 23 11:32:15 CEST 2008


As you can see the the to dates are not exactly equal, although they should, so it is hard to compare them without goofing around with return value of getTime. I also tried java.sql.Date, Timestamp and date instead of timestamp in the mapping, but without success.

I wonder why the last three digits are zero and if this is a hibernate or a java issue or my own stupidity.

Thank you for reading.


public class Clock {

    int id;
    java.util.Date date;

    public static void main(String[] args) {

        Clock clock = new Clock(); = new java.util.Date();



        Clock fromDBClock = (Clock)HibernateUtil.getSessionFactory()
                        .getCurrentSession().get(Clock.class, 1);







    public int getId() {
        return id;

    public void setId(int id) { = id;

    public java.util.Date getDate() {
        return date;

    public void setDate(java.util.Date date) { = date;



<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
        "-//Hibernate/Hibernate Mapping DTD 3.0//EN"


    <class name="Clock" table="CLOCK">
        <id name="id" column="CLOCK_ID">
            <generator class="native"/>
        <property name="date" type="timestamp"/>



Asked by: Grace136 | Posted: 21-01-2022

Answer 1

MySql DateTime precision is only to the second. Java Date precision is to the millisecond. That is why the last three digits are zeros after it has been put in the database.

Do this to your original Date:

date = date.setTime((date.getTime() / 1000) * 1000);

This will set it to the last exact second, and all your comparisons will then match.

(BTW, System.out.println(fromDBClock.toString()); should be System.out.println(;

Answered by: Michael630 | Posted: 22-02-2022

Answer 2

SQL Server stores datetime with a precision of 3 milliseconds which can definitely cause the problem you're seeing. One fallout of this is that 23:59:59.999 in Java ends up being the next day in SQL Server. I've never had a problem with Oracle, Informix, or MySQL, but other databases may have less precision also. You can work around it by using Hibernate custom types. You have to round to something less precise than the underlying database precision when you write out the date values. Search for UserType in the Hibernate documentation, you'll be changing the nullSafeSet method to do the rounding.

Answered by: Sawyer776 | Posted: 22-02-2022

Answer 3

Apparently, TIMESTAMP type on your target RDBMS (what are you using, btw?) doesn't store milliseconds. Try to find another native type that does, or map your time onto something else, like long = ms-since-epoch.

Answered by: Brad947 | Posted: 22-02-2022

Answer 4

Personnaly, I truncate every date I receive in my POJO object with the Apache commons lang package class named DateUtils.

See [Apache commons site][1]

[1]:, int)

Answered by: Edgar841 | Posted: 22-02-2022

Similar questions

Still can't find your answer? Check out these amazing Java communities for help...

Java Reddit Community | Java Help Reddit Community | Java Community | Java Discord | Java Programmers (Facebook) | Java developers (Facebook)