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.

Bug 64165 - Oracle TIMESTAMP is not displayed properly.
Summary: Oracle TIMESTAMP is not displayed properly.
Status: CLOSED FIXED
Alias: None
Product: db
Classification: Unclassified
Component: SQL Editor (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: Andrei Badea
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-12 22:46 UTC by reedb2005
Modified: 2006-03-24 13:07 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description reedb2005 2005-09-12 22:46:12 UTC
TIMESTAMP elements are currently displayed as 'oracle.sql.TIMESTAMP@xxx'. 
Please take a moment to implement toString() or invoke the appropriate method to
convert the retrieved timestamps to something useful.

Thanks!  :)
Comment 2 Andrei Badea 2005-09-13 14:49:14 UTC
Forgot to mark as fixed.
Comment 3 Martin Schovanek 2005-11-21 11:57:34 UTC
VERIFIED
Comment 4 dynamite 2005-11-27 11:08:31 UTC
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.
Comment 5 Andrei Badea 2005-12-16 17:18:42 UTC
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.