From 057aba38426f5743cfe3284c2fa40f3f9189e6a2 Mon Sep 17 00:00:00 2001 From: tjchambers Date: Fri, 4 Jan 2013 21:01:57 -0500 Subject: [PATCH] Update README.markdown --- README.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.markdown b/README.markdown index 497c0bf..57cfd96 100644 --- a/README.markdown +++ b/README.markdown @@ -84,7 +84,7 @@ For support or to discuss development please use the [Google Group](http://group ## What strategy is fastest? -For the SQL libraries the fastest option will be to use `:transaction` as transactions are simply rolled back. If you can use this strategy you should. However, if you wind up needing to use multiple database connections in your tests (i.e. your tests run in a different proceess than your application) then using this strategy becomes a bit more difficult. You can get around the problem a number of ways. +For the SQL libraries the fastest option will be to use `:transaction` as transactions are simply rolled back. If you can use this strategy you should. However, if you wind up needing to use multiple database connections in your tests (i.e. your tests run in a different process than your application) then using this strategy becomes a bit more difficult. You can get around the problem a number of ways. One common approach is to force all processes to use the same database connection ([common ActiveRecord hack](http://blog.plataformatec.com.br/2011/12/three-tips-to-improve-the-performance-of-your-test-suite/)) however this approach has been reported to result in non-deterministic failures.