Hi,
I've encountered an error message "-7040: Referential constraint not allowed" with an
ALTER TABLE command. And after studied the reference manual, seems that there is a
strict rule for the "Referential Constraint Definition". Although I'm not fully
understand the reason, but seems that this can help to avoid some referential
integrity problem.
However, in my case, I'm now porting a database from ORACLE to MAXDB. Unfortunately,
the database schema in ORACLE contains quite a number of such referential constraint
definitions. It means that ORACLE allows it to exist. Also, I've found that certain
users have already brought such issue into the forum.
Actually, I would like to suggest to add a FLAG or OPTION for user to control whether
to enable or disable such rule during database instantiation (and of course, those who
choose to disable the rule should suffer on their own if referential integrity problem
occurs). Or is there any better work around?
Thanks!
Regards,
Wing
---------------------------------
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
