Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Mylyn/Incubator/Generic Industrial Connector"
(→Plan) |
(→Screenshots) |
||
Line 65: | Line 65: | ||
Image:Mylyn_sql_1.png|Full Workbench showing all relevant structures | Image:Mylyn_sql_1.png|Full Workbench showing all relevant structures | ||
Image:Dbconfig.png|New Repository Wizard | Image:Dbconfig.png|New Repository Wizard | ||
+ | Image:SqlTaskEditor.png|SQL Task Editor | ||
</gallery> | </gallery> |
Revision as of 08:26, 22 March 2008
This work is funded by Remain Software and Industrial-TSI.
This is a temp doc space for the generic SQL connector for mylyn.
Contents
Temporary SVN
svn://bugs.industrial-tsi.com/mylyn_gsc
Members
Maarten Meijer
Wim Jongman
Plan
Initial Request: bug 184532
Discussion: bug 223048
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.
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.
But how?
Task Context
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
and possibly:
- in the list of TaskComments and - in the list of TaskAttachments.
Screenshots
- SqlTaskEditor.png
SQL Task Editor