From 00a54edabd5a58e81c0364bd8ca940c5d227be6a Mon Sep 17 00:00:00 2001
From: Gareth Rushgrove <gareth@morethanseven.net>
Date: Sun, 24 Oct 2010 13:22:18 +0100
Subject: [PATCH] added warning as per issue 13 re: nodb test runner option

---
 README.textile | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/README.textile b/README.textile
index 87d05be..ed4ee0a 100644
--- a/README.textile
+++ b/README.textile
@@ -51,6 +51,8 @@ Sometimes your don't want the overhead of setting up a database during testing,
 <pre>python manage.py test --nodb --coverage</pre>
 <pre>python manage.py test --nodb --xmlcoverage</pre>
 
+*WARNING* Don't use this if you use the ORM in your app. An "outstanding issue":http://github.com/garethr/django-test-extensions/issues#issue/13 means that you can get into trouble. Your tests will still hit the database, but it will be your non test data. 
+
 h2. Local Continuous Integration Command
 
 Thanks to Roberto Aguilar (http://github.com/rca) for providing a auto-reloading version of the test runner. Run the runtester command and it should run your test suite whenever you change a file (similar to how runserver reloads the server each time you change something.)