Kbase 19097: Importing schema by task - schema integrity violation
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/2/1999 |
|
Importing schema by task - schema integrity violation
SUMMARY: Importing schema by task - schema integrity violation
Knowledge Base number: 19097
This document applies to: Roundtable
Importing schema by task is a dangerous business. You should only
import schema changes as a base line (by release).
If your current process is to allow developers to make many schema
changes, but only approved changes get moved forward, then you should
use schema sandboxes (see the white-paper on schema sandboxes
http://www.roundtable-tsms.com.
Consider the following example:
Task 1
---------
PDBASE sports V020000 is created and is assigned the items2 table.
TASK 2
----------
PDBASE sports V030000 is created and is assigned the customer2 table.
If you try to import task 2, you will get a schema integrity
violation.
V030000 contains the items2 table as well as the customer2 table.
You are only importing the PDBASE sports V030000 and the customer2
table. Items2 does not exist in the target workspace and will not
will not exist after the import, so RTB will not allow the import.
There is no way to import JUST second change. V030000 of the sports
PDBASE object is supposed to have both tables in it.
GW - ama