Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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"
| Line 10: | Line 10: | ||
==Plan== | ==Plan== | ||
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=184532 bug 184532] | [https://bugs.eclipse.org/bugs/show_bug.cgi?id=184532 bug 184532] | ||
| + | |||
| + | ==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? | ||
| + | |||
| + | ==Generic Query Structure to map to any SQl DB== | ||
| + | There will be a Query window allowing (full text) selection on: | ||
| + | |||
| + | - repositoryUrl | ||
| + | - taskId | ||
| + | - owner | ||
| + | - summary | ||
| + | - priority (as P1, P2, P3, P4 or P5) | ||
| + | - completed | ||
| + | - completionDate (null is not completed) | ||
| + | - creationDate | ||
| + | - dueDate | ||
| + | - notes | ||
| + | |||
| + | and possibly: | ||
| + | |||
| + | - in the list of TaskComments and | ||
| + | - in the list of TaskAttachments. | ||
Revision as of 17:20, 12 March 2008
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
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?
Generic Query Structure to map to any SQl DB
There will be a Query window allowing (full text) selection on:
- repositoryUrl - taskId - owner - summary - priority (as P1, P2, P3, P4 or P5) - completed - completionDate (null is not completed) - creationDate - dueDate - notes
and possibly:
- in the list of TaskComments and - in the list of TaskAttachments.