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"
m (→Requirements) |
(→Requirements) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
==Requirements== | ==Requirements== | ||
| − | Following items have been identified as potential candidate requirements for the Visual SQL Builder | + | Following items have been identified as potential candidate requirements for the SQL Query Builder (pka Visual SQL Builder). Details on each requirement can be found in the pdf document attached to [https://bugs.eclipse.org/bugs/show_bug.cgi?id=188528 this BugZilla entry]. |
*Functional Requirements | *Functional Requirements | ||
** Create a SQL Statement. | ** Create a SQL Statement. | ||
** Create a complex SQL Statement | ** Create a complex SQL Statement | ||
| − | ** Execute current SQL statement from within | + | ** Execute current SQL statement from within SQL Query Builder |
| − | ** Integration with SQL Execution Plan framework for the current statement in | + | ** Integration with SQL Execution Plan framework for the current statement in SQL Query Builder |
** Visually edit/modify an existing SQL statement | ** Visually edit/modify an existing SQL statement | ||
** Use an existing SQL statement template to build a SQL statement | ** Use an existing SQL statement template to build a SQL statement | ||
| Line 14: | Line 14: | ||
* UI Design Requirements | * UI Design Requirements | ||
| − | ** Launch/integrate | + | ** Launch/integrate SQB in different places, including as wizard pages or preference pages in a dialog |
** Quick and easy access to database objects | ** Quick and easy access to database objects | ||
| − | ** SQL Editor and | + | ** SQL Editor and SQB Integration |
| − | ** Enhancements in | + | ** Enhancements in SQB Visual panel |
| − | ** Enhancements in | + | ** Enhancements in SQB Source panel |
* Framework Requirements | * Framework Requirements | ||
| − | ** | + | ** SQB 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 SQB |
** 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 | + | ** Basic SQB 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 | ||
Latest revision as of 13:05, 25 September 2007
← Back to SQL Development Tools page
Requirements
Following items have been identified as potential candidate requirements for the SQL Query Builder (pka Visual SQL Builder). 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 SQL Query Builder
- Integration with SQL Execution Plan framework for the current statement in SQL Query 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 SQB in different places, including as wizard pages or preference pages in a dialog
- Quick and easy access to database objects
- SQL Editor and SQB Integration
- Enhancements in SQB Visual panel
- Enhancements in SQB Source panel
- Framework Requirements
- SQB 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 SQB
- Plug-ability of Vendor database specific fixed language objects
- General purpose catalog loading mechanism to hook up various objects loading support.
- Basic SQB functionality should work for any vendor database without requiring any changes
- Vendor-neutrality, ease of adoption, and backward compatibility