From fd8c38435e68cfcaeab90398e09e58b0fa15d127 Mon Sep 17 00:00:00 2001 From: Frederick Cheung Date: Tue, 9 Sep 2008 02:13:18 +0100 Subject: typo --- railties/doc/guides/migrations/migrations.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'railties/doc/guides/migrations/migrations.txt') diff --git a/railties/doc/guides/migrations/migrations.txt b/railties/doc/guides/migrations/migrations.txt index ad20dcdf93..d7087d4044 100644 --- a/railties/doc/guides/migrations/migrations.txt +++ b/railties/doc/guides/migrations/migrations.txt @@ -1,9 +1,9 @@ Migrations ========== -Migrations are a convenient way for you to alter your database in a structured and organised manner. While you could edit fragments of SQL by hand it would then be up to you to tell other developers that they need to run your scripts when they next pull changes. You'd also have to keep track of which changes need to be run against the production machines next time you deploy. Active Record tracks which migrations have already been run so all you have to do is update your source and run `rake db:migrate`. Active Record will work out which migrations should be run. +Migrations are a convenient way for you to alter your database in a structured and organised manner. You could edit fragments of SQL by hand but you would then be responsible for telling other developers that they need to go and run it. You'd also have to keep track of which changes need to be run against the production machines next time you deploy. Active Record tracks which migrations have already been run so all you have to do is update your source and run `rake db:migrate`. Active Record will work out which migrations should be run. -Migrations also allow you to describe these transformation using ruby. The great thing about this is that (like most of Active Record's functionality) its database independent, you don't need to worry about the precise syntax of CREATE TABLE any more that you worry about variations on SELECT * (you can drop down to raw SQL for database specific features). For example you could use SQLite3 in development, but MySQL in production. +Migrations also allow you to describe these transformations using ruby. The great thing about this is that (like most of Active Record's functionality) its database independent, you don't need to worry about the precise syntax of CREATE TABLE any more that you worry about variations on SELECT * (you can drop down to raw SQL for database specific features). For example you could use SQLite3 in development, but MySQL in production. You'll learn all about migrations including: @@ -17,4 +17,5 @@ include::creating_a_migration.txt[] include::writing_a_migration.txt[] include::rakeing_around.txt[] include::using_models_in_migrations.txt[] -include::scheming.txt[] \ No newline at end of file +include::scheming.txt[] +include::foreign_keys.txt[] \ No newline at end of file -- cgit v1.2.3