I have a large project that's about to switch databases, from Postgres to mysql... I'm planning to store dates in long int columns because of mysql's lack of date precision. Using a custom UserType works fine, but I've found that I now need to call Query.setParameter(String, String, Type) instead of setDate()...

I looked into how to override what type setDate() or setTimestamp() uses.. but I came up empty handed. It appears that the implementations for the types, including the QueryImpl, and SessionImpl classes.. are pretty hard-coded.

Is there a pattern for accomplishing what I'm looking for? I'm definitely a bit surprised, since this is an ORM that supports quite a bit of custom type definition... I'd like not to have to convert the codebase to use the setParameter() method. I'd love to make this change more seamless than that.

Thanks in advance,
Phill

Why not simply use

where <param value> is your date object - no need to tell the type - Hibernate is clever enough to discover it and use the UserType you defined.

For your info, I've implemented such a user type for dates as you described and I'm passing the parameters to the query as explained above without any problems...

Thanks.. I didn't know that, actually.. I assumed it might have resulted in the same thing as setDate()...

The challenge I'm having is that I have a team of people used to calling setDate() and I'd like to make this change as seamless as possible.

Since everywhere in our codebase gets Session instances through a HibernateUtil class of ours (like pretty much everyone else who uses Hibernate, I imagine)...

Last night I created Session & Query wrappers that simply delegate all method calls through, massaging the setDate() into setParameter()..

Not sure how I feel about it yet, but it works of course :)