%NOCHECK for Objects

Question

Question

NinaNif10 · Mar 31

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.

Product version: IRIS 2024.1

Discussion (1)1

Log in or sign up to continue

score 0 · Answer 1 · 2025-03-31T15:16:42-04:00

When batch inserting data into a table via SQL, you can use the %NOCHECK keyword to avoid checking foreign key integrity. However, when inserting via objects, there isn't a direct equivalent to %NOCHECK. еуыелоивалопмва

One workaround is to use the $SYSTEM.SQL.SetFilerRefIntegrity() method to disable foreign key referential integrity checking. Alternatively, you can define a foreign key on the table using the NoCheck keyword so that foreign key referential integrity checking is never performed [1][2].

For more detailed steps on how to implement these methods, please refer to the relevant documentation.