Mylyn/Incubator/Generic Industrial Connector
This is a temp doc space for the generic SQL connector for mylyn.
We have created an update site at http://bugs.industrial-tsi.com/mylyndb/ to try this connector for 3.0.x and 2.3.x.
The port of the generic SQL connector to Mylyn 3.0 will be at:
The generic SQL connector for Mylyn 2.3.x will be at:
Current work is done using Apache Ibatis so that all configuration can be stored in the ibatis xml configuration files.
Legal parameter sets for various fields can then be stored as pseudo queries.
News from the dev team
* 06/21 Restructured the SVN to start porting to Mylyn 3.0 * 06/13 Now ready to create tasks as well, using a property in the db.properties to allow this. Only how to set the properties in the new task editor? * 06/10 Well I have refactored the code and project structure, so now basically settings for every database are in a Fragment.
This increases modularity and offers the possibility of adding code fragments for specific databases, adds a speciic home for JDBC drivers, etc.
* 09/08 Port to 3.0 is underway, new preliminary package names: org.eclipse.mylyn.sql.* * 09/26 New version 0.7.0.v20080926 with extended queryEditor and general UI improvements, download site available
Generic Task Structure to map to any SQL DB
These are mainly the fields from AbstractTask
- repositoryUrl - taskId - owner - summary - priority (as P1, P2, P3, P4 or P5) - completed - completionDate (null is not completed) - creationDate - dueDate - notes
Further more a generic Task can hold:
- a list of TaskComments and - a list of TaskAttachments.
Since the users of this connector are owners of the database (otherwise they would not be able to access it) it makes sense to create a new table that is keyed by task id and that holds a blob for the task context. In this way the task context can conveniently be dropped in this table. This could also be a setting in the connector.
Generic Query Structure to map to any SQL DB
There will be a Query window allowing (full text) selection on:
- taskId : match a specific ID - owner : match a known owner from a list - summary : match a string in a description - priority (as P1, P2, P3, P4 or P5) : match one or more priorities - completed : match true or false - completionDate (null is not completed) : match before, after and null - creationDate : match before, after and null - dueDate : match before, after and null - notes : match a string in a description
- in the list of TaskComments and - in the list of TaskAttachments.