Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m trying to understand whether the situation best described in SQL below is a WTF or a hack of some sort:
alter table CORE_FIELD
add constraint R_106 foreign key (CO_FIELD_ID)
references CORE_FIELD (CO_FIELD_ID) on delete set null;
Database: Oracle 11.2.0.1
I can’t think of anything meaningful that would be accomplished by such a constraint. Obviously the constraint would always be satisfied so it does not serve an integrity function. I had a thought that maybe it was a hacky way of preventing deletions, but it doesn’t do that in my experiments.