As far as the Sample Contents and Data
Editor features, I would say that this is a defect. These features
should be aware of the whether or not schema are supported. Please
open two defects for this, one against Sample Contents and one against
the Data Editor.
Generally, since the supportsSchema()
method is available from the Database Definition, all DTP features should
be checking this as necessary in order to provide the proper behavior.
RAD Data Tools, DB2 Tooling, Eclipse WTP Project and Eclipse DTP
IBM DB2 Information Management Software
Roman Rokytskyy <rrokytskyy@xxxxxxxxxxx> Sent by: dtp-dev-bounces@xxxxxxxxxxx
02/19/2007 05:54 AM
Please respond to
DTP development mailing list <dtp-dev@xxxxxxxxxxx>
[dtp-dev] Firebird enablement in DTP
Let me first introduce myself. I am currently main developer of the
Firebird's JDBC driver (Jaybird) as well as one of the admins of the
I have already sent this email to dtp-connect-dev list, but this seems
to be more active compared to that one. Sorry for crossposting.
Right now I am trying to add support for Firebird RDBMS to DTP and
experience some problem. The main specifics of the Firebird is that is
does not support schemas. I have created appropriate extensions of the
org.eclipse.datatools.connectivity.driverExtension extension point and
it works - DTP is able to load and show the database objects.
The next problem are the Data->Sample Contents, Data->Edit and similar
functionality. I have discovered that in many places DTP generates the
qualified name of the table by using schemaName + "." + tableName
ignoring the "Schema supported" setting in the corresponding
At this point I have started checking whether I can override the
functionality by creating my own plugin that would reuse existing DTP
code and override some methods (e.g. TableDataEditor.initDbOutputItem()).
I have subclassed the ProfileActionsActionProvider and the
DataSourceExplorerView classes and configured the appropriate extension
points in the plugin. However, I experience one problem - my custom view
contains the registered profile nodes, but when I connect to the
database, the tree content is updated in the original DSE view, not in
my customized one. I have spent some time to solve the issue, but with
Now it is time to ask questions :)
a) is there any way to tell DTP not to use schema when computing
qualified names without directly modifying the DTP sources?
b) assuming that overriding those methods is the only possibility to
solve the issue, where can I get help about subclassing/customizing the
DSE and related classes?
Thanks a lot in advance!
dtp-dev mailing list