I notice that the modeler is unable to create a constraint across a schema, even when the two schemas are in the same database. Is this to be expected? If so, should the modeler stop generating these kinds of statements?
[SQL: ALTER TABLE ENG_WORK_MGMT.ENG_WORK ADD FOREIGN KEY (ENG_WORK_ID) REFERENCES CORE_WORK_MGMT.STATUSABLE_WORK (ID)] - ORA-00942: table or view does not exist [SQL: ALTER TABLE ENG_WORK_MGMT.WOMS_WORK ADD FOREIGN KEY (WOMS_WORK_ID) REFERENCES CORE_WORK_MGMT.STATUSABLE_WORK (ID)] - ORA-00942: table or view does not exist [SQL: ALTER TABLE ENG_WORK_MGMT.AUTHORIZATION_DOCUMENT ADD FOREIGN KEY (RIGHT_OF_WAY_SECROLE_ID) REFERENCES ADMINDB.SEC_ROLE (ID)] - ORA-00942: table or view does not exist [SQL: ALTER TABLE ENG_WORK_MGMT.AUTHORIZATION_DOC__WORK ADD FOREIGN KEY (WORK_ID) REFERENCES CORE_WORK_MGMT.WORK (ID)] - ORA-00942: table or view does not exist
