Will I suffer consequences later if I add FKs with ON DELETE CASCADE and such?
If not, what naming convention should I be using for FKs within MySQL for CakePHP?
Share
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.
Will I suffer consequences later if I add FKs with ON DELETE CASCADE and such?
If not, what naming convention should I be using for FKs within MySQL for CakePHP?
You can see the naming conventions laid out here.
Cake handles FK/relationships in the code, based on your model associations and implied associations by naming conventions. You can add an extra layer of “enforcement” by defining FK relationships on the database level. If your database honours these, it’s harder to shoot yourself in the foot, but it’s not necessary. It adds the extra overhead of keeping the relationships in sync in Cake’s models and in the database.