we face the following situation which is pretty much the same as in [this thread|http://forums.oracle.com/forums/thread.jspa?messageID=1971959].
- we have a version enabled table X
- we have another table Y which is not version enabled
- we want to insert a FK from X to Y (so Y would be a parent table)
this is currently not possible because Y is not version enabled.
our question now is: would it be possible to version enable Y (and possible any other tables that reference it) temporarily, then add the FK from X to Y and then version disable Y (and all other tables that reference it) again?
this would be a very simple solution, that's why we think there is a pitfall as the possibility was also not mentioned in the thread linked above :)
it would be important for us, that we can restore exactly the versioning-situation as it was before the modifications, i.e. no additional tables stay versioned.
any comments on this are appreciated.
Yes, it would be possible to temporarily execute dbms_wm.enableversioning on the parent table. At least in most cases. If the table that you want to add as the child, is itself a parent to a 3rd table, and the new constraint is defined as 'on delete cascade', then we would not allow the grand-parent table to be disable versioned, without diasable versioning the other tables in the RIC set. Other than that case however, everything you are suggesting should work as expected.