Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "SQL Dev Tools Callisto Features"

(The following features are ''under consideration'' for SQL Dev Tools Callisto:)
 
(4 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
←[[SQL Development Tools | Back to SQL Dev Main Page]]
 
←[[SQL Development Tools | Back to SQL Dev Main Page]]
 +
{{Callisto Deprecation Notice}}
 
===The following features are committed for SQL Dev Tools Callisto:===
 
===The following features are committed for SQL Dev Tools Callisto:===
 +
====JUnit Tests====
 +
<PMC>Add JUnit tests to SQL Dev</PMC>
 +
====SQL Editor Framework====
 +
* '''Toggle comment'''
 +
** Requirement: Add context menu in SQL Editor to toggle sql statement comment
 +
** Development Estimate: 2 days
 +
** Possible Start Date: May 15
 +
** API Impacts: None
 +
** UI Impacts: None.
 +
====SQL Results View====
 +
* '''Add some methods to support WTP Outputview's current consumers'''
 +
** Requirement: Currently, WTP Output view's current consumers need some extra APIs which are not contained in current SQL Results  View's API, we need to support some of them to lessen the refactoring effort of Output view's consumers
 +
** Development Estimate: 6~9 days
 +
** Possible Start Date: April 10
 +
** API Impacts: org.eclipse.datatools.sqltools.result.ResultsViewAPI
 
===The following features are ''under consideration'' for SQL Dev Tools Callisto:===
 
===The following features are ''under consideration'' for SQL Dev Tools Callisto:===
 
====SQL Editor Framework====
 
====SQL Editor Framework====
Line 12: Line 28:
 
** API Impacts: None
 
** API Impacts: None
 
** UI Impacts: None.
 
** UI Impacts: None.
 +
<PMC>This seems to have UI impact.</PMC>
  
 
* '''Templates'''
 
* '''Templates'''
Line 17: Line 34:
 
** Development Estimate: 1 week
 
** Development Estimate: 1 week
 
** Possible Start Date: May 8
 
** Possible Start Date: May 8
** API Impacts: None
 
** UI Impacts: None.
 
 
* '''Toggle comment'''
 
** Requirement: Add context menu in SQL Editor to toggle sql statement comment
 
** Development Estimate: 2 days
 
** Possible Start Date: May 15
 
 
** API Impacts: None
 
** API Impacts: None
 
** UI Impacts: None.
 
** UI Impacts: None.
Line 33: Line 43:
 
** API Impacts: None
 
** API Impacts: None
 
** UI Impacts: None.
 
** UI Impacts: None.
 +
<PMC>This seems to have UI impact.</PMC>
  
===SQL Results View===
+
====SQL Results View====
 
* '''Add "Save History..." context menu in for script history'''
 
* '''Add "Save History..." context menu in for script history'''
 
** Requirement: Save the history into a external file which include: script, messages, parameters, results.
 
** Requirement: Save the history into a external file which include: script, messages, parameters, results.
Line 40: Line 51:
 
** Possible Start Date: Post April 9
 
** Possible Start Date: Post April 9
 
** API Impacts: None
 
** API Impacts: None
 
* '''Add some methods to support WTP Outputview's current consumers'''
 
** Requirement: Currently, WTP Output view's current consumers need some extra APIs which are not contained in current SQL Results  View's API, we need to support some of them to lessen the refactoring effort of Output view's consumers
 
** Development Estimate: 6~9 days
 
** Possible Start Date: April 10
 
** API Impacts: org.eclipse.datatools.sqltools.result.ResultsViewAPI
 

Latest revision as of 22:56, 26 August 2007

Back to SQL Dev Main Page

Note: This page discusses topics related to the 2006 Callisto Simultaneous Release. Most of the Callisto pages are deprecated. You are urged to find current information on pages related to the 2007 effort, currently named the Europa Simultaneous Release.

The following features are committed for SQL Dev Tools Callisto:

JUnit Tests

<PMC>Add JUnit tests to SQL Dev</PMC>

SQL Editor Framework

  • Toggle comment
    • Requirement: Add context menu in SQL Editor to toggle sql statement comment
    • Development Estimate: 2 days
    • Possible Start Date: May 15
    • API Impacts: None
    • UI Impacts: None.

SQL Results View

  • Add some methods to support WTP Outputview's current consumers
    • Requirement: Currently, WTP Output view's current consumers need some extra APIs which are not contained in current SQL Results View's API, we need to support some of them to lessen the refactoring effort of Output view's consumers
    • Development Estimate: 6~9 days
    • Possible Start Date: April 10
    • API Impacts: org.eclipse.datatools.sqltools.result.ResultsViewAPI

The following features are under consideration for SQL Dev Tools Callisto:

SQL Editor Framework

  • Add preferences pages
    • Requirement: Allow user to config SQL Dev Tools including
      • sql execution preference page: whether to continue when error occurs during sql execution
      • SQL Editor preference page: show affordance in hover on how to make it sticky
      • SQL template preference page: create, edit or remove templates
    • Development Estimate: 2 weeks
    • Possible Start Date: April 17
    • API Impacts: None
    • UI Impacts: None.

<PMC>This seems to have UI impact.</PMC>

  • Templates
    • Requirement: make code template available in content assist add context menu in SQL Editor to "Save as template..."
    • Development Estimate: 1 week
    • Possible Start Date: May 8
    • API Impacts: None
    • UI Impacts: None.
  • Toolbar
    • Requirement: show some of the most frequently used sql editor context menu to the toolbar, which is requested by Jeff in bug: 81036
    • Development Estimate: 3 days
    • Possible Start Date: May 24
    • API Impacts: None
    • UI Impacts: None.

<PMC>This seems to have UI impact.</PMC>

SQL Results View

  • Add "Save History..." context menu in for script history
    • Requirement: Save the history into a external file which include: script, messages, parameters, results.
    • Development Estimate: 1 day
    • Possible Start Date: Post April 9
    • API Impacts: None

Back to the top