This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Oracle TIMESTAMP is not displayed properly. | ||
---|---|---|---|
Product: | db | Reporter: | reedb2005 <reedb2005> |
Component: | SQL Editor | Assignee: | Andrei Badea <abadea> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | dynamite |
Priority: | P3 | ||
Version: | 4.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
reedb2005
2005-09-12 22:46:12 UTC
Forgot to mark as fixed. VERIFIED This is not fixed. Oracle mis-uses timestamps to store dates and times as well as timestamps. The issue-raiser may be happy if he is storing dates, but if he stores times all he'll ever see with this fix is 1970-01-01! A timestamp is a combination of date and time, whereas ResultSet.getDate() truncates the time part. ResultSet.getTimestamp() is the correct call into ResultSet to retrieve the complete information. The real issue is that Oracle don't seem to provide a correct implementation of toString(). This can be over come by converting it explicitly to an actual Date instance. I'm going to try a fix of this tomorrow. To dynamite: you are right, but I did not catch this since you forgot to reopen the issue. This problem was filed as issue 70521. |