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 "Visual SQL Builder Requirements"
(→Requirements) |
(→Requirements) |
||
| Line 12: | Line 12: | ||
* UI Design Requirements | * UI Design Requirements | ||
| − | ** Launch/integrate VSB in different places | + | ** Launch/integrate VSB in different places |
| − | ** Quick and easy access to database objects | + | ** Quick and easy access to database objects |
** SQL Editor and VSB Integration | ** SQL Editor and VSB Integration | ||
** Enhancements in VSB Visual panel | ** Enhancements in VSB Visual panel | ||
| Line 19: | Line 19: | ||
* Framework Requirements | * Framework Requirements | ||
| − | ** VSB must be designed so that adopters can enable it for their own database SQL, and such that their enablement work isn’t invalidated by future work on the core VSB | + | ** VSB must be designed so that adopters can enable it for their own database SQL, and such that their enablement work isn’t invalidated by future work on the core VSB |
** Plug-ability of Vendor database specific fixed language objects | ** Plug-ability of Vendor database specific fixed language objects | ||
** General purpose catalog loading mechanism to hook up various objects loading support. | ** General purpose catalog loading mechanism to hook up various objects loading support. | ||
| − | ** Basic VSB functionality should work for any vendor database without requiring any changes | + | ** Basic VSB functionality should work for any vendor database without requiring any changes |
| − | ** Vendor-neutrality, ease of adoption, and backward compatibility | + | ** Vendor-neutrality, ease of adoption, and backward compatibility |
Revision as of 20:36, 22 May 2007
Requirements
Following items have been identified as potential candidate requirements for the Visual SQL Builder tool. Details on each requirement can be found in the pdf document attached to this BugZilla entry.
- Functional Requirements
- Create a SQL Statement.
- Create a complex SQL Statement
- Execute current SQL statement from within Visual SQL Builder
- Integration with SQL Execution Plan framework for the current statement in Visual SQL Builder
- Visually edit/modify an existing SQL statement
- Use an existing SQL statement template to build a SQL statement
- Build WHERE/HAVING clause expressions and conditions
- UI Design Requirements
- Launch/integrate VSB in different places
- Quick and easy access to database objects
- SQL Editor and VSB Integration
- Enhancements in VSB Visual panel
- Enhancements in VSB Source panel
- Framework Requirements
- VSB must be designed so that adopters can enable it for their own database SQL, and such that their enablement work isn’t invalidated by future work on the core VSB
- Plug-ability of Vendor database specific fixed language objects
- General purpose catalog loading mechanism to hook up various objects loading support.
- Basic VSB functionality should work for any vendor database without requiring any changes
- Vendor-neutrality, ease of adoption, and backward compatibility