recommendation: use the 「no load」 option for nicknames with referential integrity constraints and load the target table outside of the replication administration tools.
推荐:为带有参照完整性约束的别名使用「noload」选项,并在复制管理工具外部装入目标表。
the target table cannot have any triggers or referential integrity constraints defined on it.
目标表不能有触发器与完整性约束。
activerecord also has trouble in some cases with referential integrity constraints because some types of associations might connect to more than one database table.
activerecord在使用参考完整性约束的某些场合也会出现问题,因为某些类型的关联可能连接到多个数据库表。
this table uses referential integrity constraints to ensure data validity.
这个表使用引用完整性约束确保数据的有效性。
replication to non-db2 target tables with referential integrity constraints is supported only if you manually define the constraints on the corresponding nicknames.
只有在相应别名上手工定义约束,才支持到带有参照完整性约束的非db2目标表的复制。
also, the q apply program does not drop referential integrity constraints on nicknames during the loading process and then restore them.
同样,在执行装入操作期间,qapply程序也不删除别名上的参照完整性约束,并在这之后恢复它们。