|
From: Jack E. <ja...@pe...> - 2006-02-17 16:32:17
|
I don't have any real help for your actual problem, but as a matter of
nitpicking, java.sql.Date granularity down to milliseconds.
-Jack Eidsness
Maury Hammel wrote:
>
> 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
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Squirrel-sql-users mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users
|
