Bug 190486 - DTP doesn't recognize Oracle columns of type TIMESTAMP
Summary: DTP doesn't recognize Oracle columns of type TIMESTAMP
Status: RESOLVED WONTFIX
Alias: None
Product: Data Tools
Classification: Tools
Component: Table Data Editor (show other bugs)
Version: 1.5   Edit
Hardware: PC Windows XP
: P3 major with 3 votes (vote)
Target Milestone: future   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-06-01 10:39 EDT by Alex Savitsky CLA
Modified: 2013-11-14 18:09 EST (History)
3 users (show)

See Also:


Attachments
error message #1 (25.17 KB, image/gif)
2007-06-01 10:40 EDT, Alex Savitsky CLA
no flags Details
error message #2 (30.44 KB, image/gif)
2007-06-01 10:40 EDT, Alex Savitsky CLA
no flags Details
table explorer view (7.05 KB, image/gif)
2007-06-01 10:41 EDT, Alex Savitsky CLA
no flags Details
original table DDL (806 bytes, text/plain)
2007-06-01 10:41 EDT, Alex Savitsky CLA
no flags Details
DTP-generated DDL (779 bytes, text/plain)
2007-06-01 10:42 EDT, Alex Savitsky CLA
no flags Details
error log export (4.22 KB, text/plain)
2007-06-01 10:44 EDT, Alex Savitsky CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Savitsky CLA 2007-06-01 10:39:44 EDT
The DTP plugin doesn't seem to properly handle columns of type TIMESTAMP.

1. When viewing table columns, TIMESTAMP columns appear as blanks (see screenshot #3)
2. When trying to enter edit mode via Data -> Edit, error messages appear (screenshot #1 then #2), and edit mode does not activate. Also, exception gets logged in the error log (see attached)
3. When generating DDL for the table, TIMESTAMP columns appear as "null" (see script.sql)

The original table DDL is attached as ddl.sql

Database is Oracle 9.2.0.4, using JDBC driver ojdbc14.jar
Eclipse is 3.3RC1, DTP version 1.5
Comment 1 Alex Savitsky CLA 2007-06-01 10:40:09 EDT
Created attachment 69699 [details]
error message #1
Comment 2 Alex Savitsky CLA 2007-06-01 10:40:40 EDT
Created attachment 69700 [details]
error message #2
Comment 3 Alex Savitsky CLA 2007-06-01 10:41:05 EDT
Created attachment 69701 [details]
table explorer view
Comment 4 Alex Savitsky CLA 2007-06-01 10:41:27 EDT
Created attachment 69702 [details]
original table DDL
Comment 5 Alex Savitsky CLA 2007-06-01 10:42:13 EDT
Created attachment 69703 [details]
DTP-generated DDL
Comment 6 Alex Savitsky CLA 2007-06-01 10:44:57 EDT
Created attachment 69705 [details]
error log export
Comment 7 Rob Cernich CLA 2007-06-01 14:33:46 EDT
The exception is coming from SQL tools.

As for the TIMESTAMP problem, I think this is an enablement concern (i.e. specialized support for Oracle).
Comment 8 Rob Cernich CLA 2007-06-01 14:34:17 EDT
changing target back to 1.5 in case the exception needs to be corrected for europa.
Comment 9 Alex Savitsky CLA 2007-06-01 14:53:47 EDT
AFAIK, TIMESTAMP is a standard SQL92 data type, not an Oracle-specific feature.
Comment 10 Hung Hsi CLA 2007-06-01 18:06:10 EDT
Problem 1-- this is caused by the catalog loader. If there does not exist Oracle SQL Model/catalog loader, then the generic SQL Model/catalog log loader caused this problem.

Problem 3-- the DDL gen code is part of the SQL Model framework, unless there exists Oracle SQL Model/Catalog Loader implementations, we cannot expect the generic catalog loader/SQL Model to generate the correct DDL code; need to extend/specialize the base SQL Model/Catalog Loader and implement the DDL Gen code.

John, please assign to the proper owner.
Comment 11 John Graham CLA 2007-06-04 10:01:24 EDT
Based on Hung's comments, this would require further enablement work for Oracle. 

For consideration in future versions of DTP Enablement.
Comment 12 Alex Savitsky CLA 2007-10-19 11:41:30 EDT
Any updates on this issue? Sorry to be persistent, but, without specialized support for real production databases, DTP has near zero usefulness
Comment 13 Michael Osipov CLA 2007-10-20 06:08:23 EDT
get http://www.oracle.com/technology/tech/eclipse/dtp
Comment 14 Alex Savitsky CLA 2007-10-22 14:12:30 EDT
Thanks!

Though it looks like there's still a long way to go towards full Oracle support (TIMESTAMP columns are RAW now, foreign keys not picked up, etc.), it's still a huge step in the right direction, as the DTP doesn't bomb out with an error anymore, at least :)

Now, did anyone in DTP team ever considered approaching Oracle for the source of their plugin? After all, Oracle itself would probably be interested in updating their plugin from DTP 1.0 to 1.5...
Comment 15 Jason Hopkins CLA 2008-03-13 07:57:17 EDT
I have a similar problem with the JTA validator, it seems to give up processing a table once it encounters a field of type timestamp.  In the Data Source Explorer it also only displays the fields of a table upto the first timestamp field.  This means that I have 97 errors in the problems view that are really not errors.
Comment 16 Brian Payton CLA 2013-11-14 18:09:41 EST
We are closing this as WONTFIX due to lack of resource to work on it.  If someone feels strongly that the problem should be fixed, please reopen, preferably with a patch for the fix.

Please see comments 13 and later about obtaining updated Oracle enablement plugins directly from Oracle.  It would be great if Oracle would contribute those to DTP.