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 "Model Base Callisto Features"
(→The following features are ''under consideration'' for Model Base Callisto:) |
(→The following features are ''under consideration'' for Model Base Callisto:) |
||
| Line 20: | Line 20: | ||
===The following features are ''under consideration'' for Model Base Callisto:=== | ===The following features are ''under consideration'' for Model Base Callisto:=== | ||
| − | 1. Export table under schema to EMF(OO definition). | + | 1. Export table under schema to EMF(OO definition).<br> |
2. Import EMF(OO definition) to Database Model. | 2. Import EMF(OO definition) to Database Model. | ||
Revision as of 12:25, 16 May 2006
← Back to Model Base Main Page
Contents
The following features are committed for Model Base Callisto:
JUnit Tests
<PMC>Add JUnit tests to SQL Dev</PMC>
Models
- Refresh DTP models for changes made in WTP/rdb
- Dates: 4/24 -- 5/01
- Impacts: Unknown
<PMC>Must determine downstream impacts before delivering this work.</PMC>
WTP Parity
- Support for new vendor docs:
- SQL Server 2005
- Sybase ASE 15
- DB2 V9
- Informix 10
- Dates: 4/24 -- 5/01
- Impacts: None
<PMC>For inclusion in planned "enablement" module.</PMC>
The following features are under consideration for Model Base Callisto:
1. Export table under schema to EMF(OO definition).
2. Import EMF(OO definition) to Database Model.