this is a repost of an earlier email i sent to the list but for some
reason didnt show up in the castor mailing list archives.
Im doing a select to read in an object with three java.util.Date fields.
The java.util.Date fields map to timestamp fields in a Postgresql 7.1
table.
<field name="startdate" type="date">
<sql name="starttime" type="timestamp" />
</field>
Executing a select statement throws this error:
Nested error: Bad Timestamp Format at 19 in 2001-08-30 23:41:13.62-07
Nested error: Bad Timestamp Format at 19 in 2001-08-30 23:42:10.72-07
If postgresql is allowed to fill in this field by using a default
timestamp, the timestamp looks like this:
2001-08-03 02:03:01-07
As you can see, at position 19 is where the dot-hundreths-of-seconds part
of the time starts. Im not sure why castor is writing the date with
hundredths of seconds but castor doesnt like to read it back out of the
database.
What can I do to avoid this error condition?
Thank You
Don Park
--
** Home web site: http://klickitat.yi.org
** BeeHive Games, Multiplayer Bluetooth PDA Gaming http://beehivegames.com
** irc: irc.openprojects.net nick: don-o channels: #palmchat,#java
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
