We're having problems controlling Materialized View definitions with Team Coding in Toad 18.104.22.168.
When a materialized view is changed -- because its query has changed for example -- it's necessary to DROP and CREATE it. We create the replacement with the same name and to all intents and purposes it's a new version.
However, checking in yields a constraint error
Error: ORA-02291: integrity constraint (TC_ADMIN.TCX_OBJHIST_OBJ_PROJ_FK) violated - parent key not found ORA-06512: at line 1
probably because the object ID has changed due to the DROP/CREATE. We're trying to check in something which is not the same object as was checked out. Even subsequent checkings-out can error in the same way, although I'm still investigating exactly what's going on there.
What is the correct way of maintaining the version history of a materialized view?