|
From: Jack E. <ja...@pe...> - 2006-02-17 17:22:17
|
Perhaps with another RDBMS, java.sql.Date ends up working as if it has no time-of-day. Almost all of my experience is with Oracle. After sending my previous mail, I noticed this text in the javadocs: "To conform with the definition of SQL DATE, the millisecond values wrapped by a java.sql.Date instance must be 'normalized' by setting the hours, minutes, seconds, and milliseconds to zero in the particular time zone with which the instance is associated." I assume they are referring to one of the SQL standards out there, but this normalization is apparently up to individual java developers (or the jdbc driver developers?), and in the case of oracle jdbc, undesirable. -Jack Eidsness Maury Hammel wrote: > Jack Eidsness wrote: >> I don't have any real help for your actual problem, but as a matter of >> nitpicking, java.sql.Date granularity down to milliseconds. > > Yep, you're right. Maybe I was thinking of java.sql.Types.DATE? > > Anyway, I know Glenn and I had a discussion about this when he > implemented the extra stuff in the Data Type Controls tab in the Global > Preferences. The Oracle DATE column is identified as a type 91, and a > type 91 doesn't allow time in the formatting. > > > 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 |
