I believe this is a problem with the java.sql.Date class; I've seen it
with Oracle as well. Try using java.sql.Timestamp instead.
Thom
David Corbin wrote:
>
> We have two date columns. One is populated by with statement similar to
> this:
>
> INSERT INTO table (FOO_DATE) VALUE ('YYYY/MM/DD HH:MM:SS');
>
> This works great.
>
> One is populated with a prepared statement:
>
> INSERT INTO table (BAR_DATE) VALUE (?),
>
> where the associated value is a java.sql.Date.
>
> The problem is that BAR_DATE always seems to throw away the time value
> (set to midnight), even after setting the database-wide default Date
> Format.
>
> Ideas?
> -----------------------------------------------------------------------------
> To unsubscribe from this mailing list, send email to majordomo@enhydra.org
> with the text "unsubscribe instantdb" in the body of the email.
> If you have other questions regarding this mailing list, send email to
> the list admin at owner-instantdb@enhydra.org.
-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-instantdb@enhydra.org.
|