stevenyap · October 18, 2025 14:39 · Feb 20, 2014 · Jan 3, 2014 · Oct 18, 2013 · Oct 18, 2013
diff --git a/Rake Database.md b/Rake Database.md
@@ -88,14 +88,14 @@ Roll back the last migration
 rake db:rollback
 ```
 
-Or you can specify how many steps (n) to rollback
+Or you can specify how many steps (n) to rollback. (Specify STEP=9999 to rollback everything)
 ```sh
-rake db:rollback step=n
+rake db:rollback STEP=n
 ```
 
 Or you can specfiy exactly the version of migration to rollback to
 ```sh
-rake db:migrate:down version=847583457438957
+rake db:migrate:down VERSION=847583457438957
 ```
 
 Or to simply rerun last migration

diff --git a/Rake Database.md b/Rake Database.md
@@ -103,4 +103,11 @@ Or to simply rerun last migration
 rake db:migrate:redo
 ```
 
-**Tip: If you are changing the latest migration, you should rake db:rollback and then add your new code to the migration file and then run rake db:migrate again**
+**Tip: If you are changing the latest migration, you should rake db:rollback and then add your new code to the migration file and then run rake db:migrate again**
+
+## Other database commands
+
+```sh
+# View all migration logs
+rake db:migrate:status
+```
diff --git a/Rake Database.md b/Rake Database.md
@@ -83,6 +83,7 @@ rake db:seed
 ```
 
 ## Roll back migration
+Roll back the last migration
 ```sh
 rake db:rollback
 ```
@@ -102,4 +103,4 @@ Or to simply rerun last migration
 rake db:migrate:redo
 ```
 
-**Tip: If you are changing the latest migration, you should rake db:rollback and then add your new code and then run rake db:migrate**
+**Tip: If you are changing the latest migration, you should rake db:rollback and then add your new code to the migration file and then run rake db:migrate again**
diff --git a/Rake Database.md b/Rake Database.md
@@ -28,6 +28,7 @@ end
 ## Run Migrate
 - You need to run migration before ROR actually creates it in the database
 - *You must run this everytime there is a new migration*  
+
 ```sh
 rake db:migrate
 ```
@@ -36,6 +37,7 @@ rake db:migrate
 - This should be ran after rake db:migrate
 - This duplicates your schema into the test database so that your test cases will work
 - Common error in test cases when you forget this step  
+
 ```sh
 rake db:test:prepare
 ```
@@ -47,11 +49,34 @@ rake db:drop
 
 ## Chaining commands
 - You can chain commands together for faster typing
+
 ```sh
 rake db:drop db:create db:migration db:test:prepare
 ```
 
 
+## Seeding the database
+- Note that seeding of database should be idempotent (running it multiple times does not create duplicated records)
+- Add your ruby commands to add data in /db/seeds.rb like below:
+
+```ruby
+puts "**  Seeding Database: seeding ***\n\n"
+
+unless User.where(email: "admin@example.com").first
+User.create!(email: 'admin@example.com',
+            password: '123123',
+            password_confirmation: '123123')
+puts "-- Created admin@example.com with password 123123\n"
+end
+
+unless Company.where(name: "ABC").first
+  Company.create!(name: "ABC")
+  puts "-- Created company: ABC\n"
+end
+
+puts "\n**  Seeding Database: completed ***"
+```
+
 Run the command below to seed the data according to seeds.rb
 ```sh
 rake db:seed

diff --git a/Rake Database.md b/Rake Database.md
@@ -27,15 +27,15 @@ end
 
 ## Run Migrate
 - You need to run migration before ROR actually creates it in the database
-- *You must run this everytime there is a new migration* 
+- *You must run this everytime there is a new migration*  
 ```sh
 rake db:migrate
 ```
 
 ## Duplicate to test database
 - This should be ran after rake db:migrate
 - This duplicates your schema into the test database so that your test cases will work
-- Common error in test cases when you forget this step
+- Common error in test cases when you forget this step  
 ```sh
 rake db:test:prepare
 ```

diff --git a/Rake Database.md b/Rake Database.md
@@ -27,7 +27,7 @@ end
 
 ## Run Migrate
 - You need to run migration before ROR actually creates it in the database
-- *You must run this everytime there is a new migration*
+- *You must run this everytime there is a new migration* 
 ```sh
 rake db:migrate
 ```

diff --git a/Rake Database.md b/Rake Database.md
@@ -51,27 +51,6 @@ rake db:drop
 rake db:drop db:create db:migration db:test:prepare
 ```
 
-## Seeding the database
-- Note that seeding of database should be idempotent (running it multiple times does not create duplicated records)
-- Add your ruby commands to add data in /db/seeds.rb like below:
-```ruby
-puts "**  Seeding Database: seeding ***\n\n"
-
-unless User.where(email: "admin@example.com").first
-User.create!(email: 'admin@example.com',
-            password: '123123',
-            password_confirmation: '123123')
-puts "-- Created admin@example.com with password 123123\n"
-end
-
-unless Company.where(name: "ABC").first
-  Company.create!(name: "ABC")
-  puts "-- Created company: ABC\n"
-end
-
-puts "\n**  Seeding Database: completed ***"
-
-```
 
 Run the command below to seed the data according to seeds.rb
 ```sh

diff --git a/Rake Database.md b/Rake Database.md
@@ -0,0 +1,101 @@
+## Create database
+```sh
+rake db:create
+```
+
+## Create database table
+This will creates a migration file in /db/migrate without table definition.  
+```sh
+rails g migration create_<TABLE>
+```
+
+Add your table definition in the file.
+```ruby
+class CreatePorts < ActiveRecord::Migration
+  def change
+    create_table :ports do |t|
+      t.string :name
+      t.text :description
+      t.string :city
+      t.string :country
+
+      t.timestamps
+    end
+  end
+end
+```
+
+## Run Migrate
+- You need to run migration before ROR actually creates it in the database
+- *You must run this everytime there is a new migration*
+```sh
+rake db:migrate
+```
+
+## Duplicate to test database
+- This should be ran after rake db:migrate
+- This duplicates your schema into the test database so that your test cases will work
+- Common error in test cases when you forget this step
+```sh
+rake db:test:prepare
+```
+
+## Drop database
+```sh
+rake db:drop
+```
+
+## Chaining commands
+- You can chain commands together for faster typing
+```sh
+rake db:drop db:create db:migration db:test:prepare
+```
+
+## Seeding the database
+- Note that seeding of database should be idempotent (running it multiple times does not create duplicated records)
+- Add your ruby commands to add data in /db/seeds.rb like below:
+```ruby
+puts "**  Seeding Database: seeding ***\n\n"
+
+unless User.where(email: "admin@example.com").first
+User.create!(email: 'admin@example.com',
+            password: '123123',
+            password_confirmation: '123123')
+puts "-- Created admin@example.com with password 123123\n"
+end
+
+unless Company.where(name: "ABC").first
+  Company.create!(name: "ABC")
+  puts "-- Created company: ABC\n"
+end
+
+puts "\n**  Seeding Database: completed ***"
+
+```
+
+Run the command below to seed the data according to seeds.rb
+```sh
+rake db:seed
+```
+
+## Roll back migration
+```sh
+rake db:rollback
+```
+
+Or you can specify how many steps (n) to rollback
+```sh
+rake db:rollback step=n
+```
+
+Or you can specfiy exactly the version of migration to rollback to
+```sh
+rake db:migrate:down version=847583457438957
+```
+
+Or to simply rerun last migration
+```sh
+rake db:migrate:redo
+```
+
+**Tip: If you are changing the latest migration, you should rake db:rollback and then add your new code and then run rake db:migrate**
No results found