What's important is that it has changed ;) The logic is better now, though. However, timestamp is required if one wants to save TIME into db and must be able to store "12:00 pm" and "06:00am next morning". Time alone cannot express 'tomorrow morning'. But in a text field input field it's better to show "06:00".
Anyways. If anybody else has used SqlTimestamp for TIME, make sure you have a test for it. ** Martin 2009/5/17 Steve Flasby <[email protected]>: > That was a Jira I raised as a result of asking about it on this list. > I did ask if there was a reason why a sql timestamp was shown as > only a time, as java.sql.xxx provides Date, Time and Timestamp. > > My understanding of this is that timestamp represents a date plus time > whereas java.sql.time is a time of day which does not specify which day. > > Am I wrong? > > > Cheers - Steve > > > Martin Makundi wrote: >> >> Hi! >> >> We were surprised to find SqlTimestampConverter changed: >> >> 1.4-rc2 DateFormat.getTimeInstance(dateFormat, locale); >> >> 1.4-rc4 DateFormat.getDateTimeInstance(dateFormat, timeFormat, locale); >> >> Maybe there could be a TimeToSqlTimestampConverter ... well, I'll just >> reuse the old class for a custom one. >> >> ** >> Martin >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
