Skip to content
This repository
Browse code

Add warning to documentation about using transactional fixtures when …

…the code under test uses transactions itself. Closes #7548 [thijsv]

git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@8303 5ecf4fe2-1ee6-0310-87b1-e25e094e27de
  • Loading branch information...
commit 15b1b889f24ee42f96b1fb74d5cab2438c32056a 1 parent 68261d4
authored December 05, 2007
2  railties/CHANGELOG
... ...
@@ -1,5 +1,7 @@
1 1
 *SVN*
2 2
 
  3
+* Add warning to documentation about using transactional fixtures when the code under test uses transactions itself. Closes #7548 [thijsv]
  4
+
3 5
 * Update Prototype to 1.6.0.1.  [sam]
4 6
 
5 7
 * Update script.aculo.us to 1.8.0.1.  [madrobby]
4  railties/helpers/test_helper.rb
@@ -15,6 +15,10 @@ class Test::Unit::TestCase
15 15
   # in MySQL.  Turn off transactional fixtures in this case; however, if you
16 16
   # don't care one way or the other, switching from MyISAM to InnoDB tables
17 17
   # is recommended.
  18
+  #
  19
+  # The only drawback to using transactional fixtures is when you actually 
  20
+  # need to test transactions.  Since your test is bracketed by a transaction,
  21
+  # any transactions started in your code will be automatically rolled back.
18 22
   self.use_transactional_fixtures = true
19 23
 
20 24
   # Instantiated fixtures are slow, but give you @david where otherwise you

0 notes on commit 15b1b88

Please sign in to comment.
Something went wrong with that request. Please try again.