I am using Calendar objects because I need to use different TimeZones. I would be storing UTC in DB but before I show it to user, I would be converting into different TimeZones. TimeZones are only supported by Calendar in java. Date and Timestamp classes do not support time zones and locales.
Thanks, Petr, --- On Fri, 1/16/09, Vadim <[email protected]> wrote: From: Vadim <[email protected]> Subject: Re: Java.util.calendar to SQLType ?? To: [email protected], [email protected] Date: Friday, January 16, 2009, 5:44 PM I wonder, what's the motivation behind making Calendar an object property? If you need some Calendar specific operations, create some accessor/mutator methods to hide the actual Calendar instance. This way you won't need explicit TypeHandlers and your implementation won't depend on the Calendar (which isn't the best piece of API for time manipulation). On Thu, Jan 15, 2009 at 10:13 PM, Petr V. <[email protected]> wrote: Database schema has column of type Timestamp . Java POJO has corresponding property defined as java.util.Calendar Result Map is defined as <resultMap class="Job" id="JobResult"> <result column="STIME" jdbcType="TIMESTAMP" javaType="java.util.Calendar" property="sTime" /> </resultMap> I understand, I would have to define typeHandler to convert jdbc type to java Calendar. I am wondering what should I define jdbcType is my sql map, should it be TimeStamp or should it be of type date. What would be the better? Thanks, Petr
