aboutsummaryrefslogtreecommitdiffstats
path: root/railties/doc/guides/migrations/foreign_keys.txt
diff options
context:
space:
mode:
authorFrederick Cheung <frederick.cheung@gmail.com>2008-09-11 14:02:45 +0100
committerFrederick Cheung <frederick.cheung@gmail.com>2008-09-11 14:02:45 +0100
commit5ad2bce12d91786486c7f476f06a5139e12046ff (patch)
treeb02981c19ce454f8e0e98e596096bc8aebf4081c /railties/doc/guides/migrations/foreign_keys.txt
parentbb52108ce8fd11cfae52a9776d33788075d0a9a8 (diff)
downloadrails-5ad2bce12d91786486c7f476f06a5139e12046ff.tar.gz
rails-5ad2bce12d91786486c7f476f06a5139e12046ff.tar.bz2
rails-5ad2bce12d91786486c7f476f06a5139e12046ff.zip
Add an example
Diffstat (limited to 'railties/doc/guides/migrations/foreign_keys.txt')
-rw-r--r--railties/doc/guides/migrations/foreign_keys.txt2
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.