From 0cfbaa030a0684aaa89d3d3c85528e80c1995836 Mon Sep 17 00:00:00 2001
From: Deepak Kannan <kannan.deepak@gmail.com>
Date: Sat, 26 May 2012 22:28:03 +0530
Subject: Small correction to contributing_to_rails in the section for testing
 ActiveRecord

Initially the guide suggests to install gems via "bundle install --without db"
But tests for ActiveRecord need to install the gems in db group also, like mysql.
The patch clears the bundler options in ".bundle/config" and installs all the gems in Gemfile
---
 guides/source/contributing_to_ruby_on_rails.textile | 6 ++++++
 1 file changed, 6 insertions(+)

(limited to 'guides/source/contributing_to_ruby_on_rails.textile')

diff --git a/guides/source/contributing_to_ruby_on_rails.textile b/guides/source/contributing_to_ruby_on_rails.textile
index 72cdea885f..8f36511d7d 100644
--- a/guides/source/contributing_to_ruby_on_rails.textile
+++ b/guides/source/contributing_to_ruby_on_rails.textile
@@ -128,6 +128,12 @@ The test suite of Active Record attempts to run four times: once for SQLite3, on
 
 WARNING: If you're working with Active Record code, you _must_ ensure that the tests pass for at least MySQL, PostgreSQL, and SQLite3. Subtle differences between the various adapters have been behind the rejection of many patches that looked OK when tested only against MySQL.
 
+NOTE: need to install gems in the db group:
+
+<shell>
+$ bundle install --without ""
+</shell>
+
 h5. Database Configuration
 
 The Active Record test suite requires a custom config file: +activerecord/test/config.yml+. An example is provided in +activerecord/test/config.example.yml+ which can be copied and used as needed for your environment.
-- 
cgit v1.2.3

