diff options
Diffstat (limited to 'railties/doc/guides/migrations/foreign_keys.txt')
| -rw-r--r-- | railties/doc/guides/migrations/foreign_keys.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/railties/doc/guides/migrations/foreign_keys.txt b/railties/doc/guides/migrations/foreign_keys.txt index 005f62a462..68c1ad7d9a 100644 --- a/railties/doc/guides/migrations/foreign_keys.txt +++ b/railties/doc/guides/migrations/foreign_keys.txt @@ -1,5 +1,5 @@ -== Active Record and Referential Integrity == [[foreign_key]] +== Active Record and Referential Integrity == The Active Record way is that intelligence belongs in your models, not in the database. As such features such as triggers or foreign key constraints, which push some of that intelligence back into the database are not heavily used. Validations such as `validates_uniqueness_of` are one way in which models can enforce data integrity. The `:dependent` option on associations allows models to automatically destroy child objects when the parent is destroyed. These cannot however guarantee referential integrity and so some people augment them with foreign key constraints. |