Author: russellm
Date: 2010-09-12 15:11:06 -0500 (Sun, 12 Sep 2010)
New Revision: 13799

Added:
   django/branches/releases/1.2.X/tests/modeltests/force_insert_update/tests.py
Modified:
   django/branches/releases/1.2.X/tests/modeltests/force_insert_update/models.py
Log:
[1.2.X] Migrated the force_insert_update tests. Thanks to Alex Gaynor.

Backport of r13782 from trunk.

Modified: 
django/branches/releases/1.2.X/tests/modeltests/force_insert_update/models.py
===================================================================
--- 
django/branches/releases/1.2.X/tests/modeltests/force_insert_update/models.py   
    2010-09-12 20:10:54 UTC (rev 13798)
+++ 
django/branches/releases/1.2.X/tests/modeltests/force_insert_update/models.py   
    2010-09-12 20:11:06 UTC (rev 13799)
@@ -11,54 +11,3 @@
 class WithCustomPK(models.Model):
     name = models.IntegerField(primary_key=True)
     value = models.IntegerField()
-
-__test__ = {"API_TESTS": """
->>> c = Counter.objects.create(name="one", value=1)
-
-# The normal case
->>> c.value = 2
->>> c.save()
-
-# Same thing, via an update
->>> c.value = 3
->>> c.save(force_update=True)
-
-# Won't work because force_update and force_insert are mutually exclusive
->>> c.value = 4
->>> c.save(force_insert=True, force_update=True)
-Traceback (most recent call last):
-...
-ValueError: Cannot force both insert and updating in model saving.
-
-# Try to update something that doesn't have a primary key in the first place.
->>> c1 = Counter(name="two", value=2)
->>> c1.save(force_update=True)
-Traceback (most recent call last):
-...
-ValueError: Cannot force an update in save() with no primary key.
-
->>> c1.save(force_insert=True)
-
-# Won't work because we can't insert a pk of the same value.
->>> sid = transaction.savepoint()
->>> c.value = 5
->>> try:
-...     c.save(force_insert=True)
-... except Exception, e:
-...     if isinstance(e, IntegrityError):
-...         print "Pass"
-...     else:
-...         print "Fail with %s" % type(e)
-Pass
->>> transaction.savepoint_rollback(sid)
-
-# Trying to update should still fail, even with manual primary keys, if the
-# data isn't in the database already.
->>> obj = WithCustomPK(name=1, value=1)
->>> obj.save(force_update=True)
-Traceback (most recent call last):
-...
-DatabaseError: ...
-
-"""
-}

Added: 
django/branches/releases/1.2.X/tests/modeltests/force_insert_update/tests.py
===================================================================
--- 
django/branches/releases/1.2.X/tests/modeltests/force_insert_update/tests.py    
                            (rev 0)
+++ 
django/branches/releases/1.2.X/tests/modeltests/force_insert_update/tests.py    
    2010-09-12 20:11:06 UTC (rev 13799)
@@ -0,0 +1,38 @@
+from django.db import transaction, IntegrityError, DatabaseError
+from django.test import TestCase
+
+from models import Counter, WithCustomPK
+
+
+class ForceTests(TestCase):
+    def test_force_update(self):
+        c = Counter.objects.create(name="one", value=1)
+        # The normal case
+
+        c.value = 2
+        c.save()
+        # Same thing, via an update
+        c.value = 3
+        c.save(force_update=True)
+
+        # Won't work because force_update and force_insert are mutually
+        # exclusive
+        c.value = 4
+        self.assertRaises(ValueError, c.save, force_insert=True, 
force_update=True)
+
+        # Try to update something that doesn't have a primary key in the first
+        # place.
+        c1 = Counter(name="two", value=2)
+        self.assertRaises(ValueError, c1.save, force_update=True)
+        c1.save(force_insert=True)
+
+        # Won't work because we can't insert a pk of the same value.
+        sid = transaction.savepoint()
+        c.value = 5
+        self.assertRaises(IntegrityError, c.save, force_insert=True)
+        transaction.savepoint_rollback(sid)
+
+        # Trying to update should still fail, even with manual primary keys, if
+        # the data isn't in the database already.
+        obj = WithCustomPK(name=1, value=1)
+        self.assertRaises(DatabaseError, obj.save, force_update=True)

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to