|
From: Maury H. <ml1...@sh...> - 2006-02-17 15:33:57
|
Mark Neher wrote:
> I'm back !! And I've found a reproducible bare bones case. The common
> thing in all of the rows that I can't edit is a non-null DATE field.
> Using the following stripped down table definition:
>
> CREATE TABLE LICENSE
> (
> NAME VARCHAR2(80),
> FILE_UPDATE_DATE DATE
> );
>
> and the following data:
>
> insert into license values ('test', null);
> insert into license values ('junk', sysdate);
>
> I can edit the 'test' row, as the DATE is null, but I get the previously
> mentioned errors when I try to save an edit in the 'junk' row. This is
> reproducible in each table in our schema that has a DATE field. BTW,
> the same problem doesn't affect TIMESTAMP fields; I can edit rows with
> non-null TIMESTAMP data.
This is probably due to the disagreement between Oracle and Java/JDBC
about dates. In Java/JDBC, a DATE (i.e. java.sql.Date) doesn't have a
time value. In Oracle it can. I'm guessing that that it would work if
you changed the insert to:
insert into license values ('junk', trunc(sysdate));
Maury
|
