Difference between revisions of "Specialized Database Support"

From Eclipsepedia

Jump to: navigation, search
Line 2: Line 2:
 
=Introduction=
 
=Introduction=
 
This document outlines the steps necessary to specialize DTP frameworks and tools in support of a specific database. The intention is to grow this document (into perhaps a family of linked documents) as community experience grows and contributes to this knowledge base. Questions, suggestions and offers for additional content are appreciated. Please use the [https://dev.eclipse.org/mailman/listinfo/dtp-dev DTP Development mailing list] or the ''Discussion'' section of this page for such conversations.
 
This document outlines the steps necessary to specialize DTP frameworks and tools in support of a specific database. The intention is to grow this document (into perhaps a family of linked documents) as community experience grows and contributes to this knowledge base. Questions, suggestions and offers for additional content are appreciated. Please use the [https://dev.eclipse.org/mailman/listinfo/dtp-dev DTP Development mailing list] or the ''Discussion'' section of this page for such conversations.
 +
=Suggested Development Environment=
 +
If you are going to do serious work extending DTP, then it will pay to have the DTP plug-ins code loaded into an Eclipse development environment, and then to run test by launching platforms from there. This will give to the ability to step through code, capture additional debug output, and generally understand what is happening much quicker than using DTP binary distributions. The current list of DTP plug-ins and instructions for Eclipse CVS access can be found [[Working with the DTP 0.9 Source | here]].
 
=Outline of Steps Required=
 
=Outline of Steps Required=
 
The amount of work necessary to support a specific database in DTP depends on the level of integration you seek. Starting out at the entry level:
 
The amount of work necessary to support a specific database in DTP depends on the level of integration you seek. Starting out at the entry level:
 
* Try to create a connection to the database using the generic JDBC connection profile. Note the level of correctness and completeness available in the resulting Data Source Explorer (DSE) tree for that database.
 
* Try to create a connection to the database using the generic JDBC connection profile. Note the level of correctness and completeness available in the resulting Data Source Explorer (DSE) tree for that database.
 
* The deviation from the completely correct answer to what has actually happened in step 1 will give you a sense of the work required.
 
* The deviation from the completely correct answer to what has actually happened in step 1 will give you a sense of the work required.

Revision as of 17:57, 17 April 2006

Back to DTP Main Page

Introduction

This document outlines the steps necessary to specialize DTP frameworks and tools in support of a specific database. The intention is to grow this document (into perhaps a family of linked documents) as community experience grows and contributes to this knowledge base. Questions, suggestions and offers for additional content are appreciated. Please use the DTP Development mailing list or the Discussion section of this page for such conversations.

Suggested Development Environment

If you are going to do serious work extending DTP, then it will pay to have the DTP plug-ins code loaded into an Eclipse development environment, and then to run test by launching platforms from there. This will give to the ability to step through code, capture additional debug output, and generally understand what is happening much quicker than using DTP binary distributions. The current list of DTP plug-ins and instructions for Eclipse CVS access can be found here.

Outline of Steps Required

The amount of work necessary to support a specific database in DTP depends on the level of integration you seek. Starting out at the entry level:

  • Try to create a connection to the database using the generic JDBC connection profile. Note the level of correctness and completeness available in the resulting Data Source Explorer (DSE) tree for that database.
  • The deviation from the completely correct answer to what has actually happened in step 1 will give you a sense of the work required.