Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Aperi Database R2 Extensibility

Revision as of 17:47, 22 January 2007 by Unnamed Poltroon (Talk)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

How do I change the database schema

This section assumes that the person is familiar with Database Component Design (MS Word).

When some database change is needed, the team member responsible for the work item (referred as the requester) will analyze the application requirements, draft the database changes on schema, helper, mapper, detectability with the help of the entire design team The requester should analyze the impact of the changes on the whole of Aperi.

The change request will be reviewed and approved by a deadline, by the design team (led by the database team lead). If needed, the committee may request consultation from special expertise area.

The requester will be responsible for the implementation of the change, and negotiate any resource issue if there is a need. The requester should test the new schema file(s) by using them to replace the corresponding files in a proper version of Aperi, then test installation, and keep the test results for record. The requester should make an overall build with all the changes to ensure nothing break, and keep the test results for record.

Back to the top