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.
Visual SQL Builder Requirements
Revision as of 20:17, 22 May 2007 by Snigam.sybase.com (Talk | contribs) (New page: == 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 attac...)
== 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 [ the 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.