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 have the same problem as in the following post.
So I am wondering, why doesn’t Rails support generating foreign keys by default?
Isn’t it necessary?
Or are we supposed to do it manually?
Database constraints aren’t required any more than wearing seat-belts are required in your car. You can drive around all you like and everything will work great until a problem arrives. The seat-belt (constraints) keep you (the data) safe.
So it’s highly recommended that you create constraints to enforce data-integrity at the database level, because it’s highly likely that 1) You will interact with the database at some point outside of Rails and 2) You will make a mistake in your code that causes invalid data.
Database constraints can be more work, but it saves a lot of work, especially when your code can make assumptions about the data and doesn’t have to do tons of validity checks.
The reason ActiveRecord doesn’t support foreign keys out of the box is because it is meant to be database-agnostic, and foreign keys are not universally supported by all database systems.