When batch inserting data into a table via SQL, I can use the %NOCHECK keyword to avoid checking foreign key integrity.  This would be appropriate for cases when the inserted data has been verified by some external process.

However, when inserting via objects, I don't see a way to get the same behavior.  Are there any workarounds that use objects for this?

For this case, I have a tool (Tier 2 CCR) for loading many objects into a namespace. The referential integrity of these objects has already be confirmed in a source namespace. Enforcing a specific load order may resolve the issue here, but generally this might not be the case.