django.git/tests/force_insert_update/tests.py, branch main

Fixed #33579 -- Specialized exception raised on forced update failures.

2025-03-10T20:09:15Z

Raising DatabaseError directly made it harder than it should to differentiate between IntegrityError when a forced update resulted in no affected rows. Introducing a specialized exception allows for callers to more easily silence, log, or turn them update failures into user facing exceptions (e.g. 404s). Thanks Mariusz for the review.

Fixed #30382 -- Allowed specifying parent classes in force_insert of Model.save().

2023-06-29T19:52:52Z

Refs #30382 -- Added more tests for using force_insert with model inheritance.

2023-06-29T09:49:32Z

Refs #33476 -- Reformatted code with Black.

2022-02-07T19:37:05Z

Used assertRaisesMessage() to test Django's error messages.

2017-07-29T23:07:23Z

Refs #23919 -- Removed encoding preambles and future imports

2017-01-18T08:55:19Z

Sorted imports with isort; refs #23860.

2015-02-06T13:16:28Z

Fixed #21134 -- Prevented queries in broken transactions.

2013-09-30T07:42:27Z

Squashed commit of the following: commit 63ddb271a44df389b2c302e421fc17b7f0529755 Author: Aymeric Augustin Date: Sun Sep 29 22:51:00 2013 +0200 Clarified interactions between atomic and exceptions. commit 2899ec299228217c876ba3aa4024e523a41c8504 Author: Aymeric Augustin Date: Sun Sep 22 22:45:32 2013 +0200 Fixed TransactionManagementError in tests. Previous commit introduced an additional check to prevent running queries in transactions that will be rolled back, which triggered a few failures in the tests. In practice using transaction.atomic instead of the low-level savepoint APIs was enough to fix the problems. commit 4a639b059ea80aeb78f7f160a7d4b9f609b9c238 Author: Aymeric Augustin Date: Tue Sep 24 22:24:17 2013 +0200 Allowed nesting constraint_checks_disabled inside atomic. Since MySQL handles transactions loosely, this isn't a problem. commit 2a4ab1cb6e83391ff7e25d08479e230ca564bfef Author: Aymeric Augustin Date: Sat Sep 21 18:43:12 2013 +0200 Prevented running queries in transactions that will be rolled back. This avoids a counter-intuitive behavior in an edge case on databases with non-atomic transaction semantics. It prevents using savepoint_rollback() inside an atomic block without calling set_rollback(False) first, which is backwards-incompatible in tests. Refs #21134. commit 8e3db393853c7ac64a445b66e57f3620a3fde7b0 Author: Aymeric Augustin Date: Sun Sep 22 22:14:17 2013 +0200 Replaced manual savepoints by atomic blocks. This ensures the rollback flag is handled consistently in internal APIs.

Removed most of absolute_import imports

2013-07-29T18:28:13Z

Should be unneeded with Python 2.7 and up. Added some unicode_literals along the way.

Merged regressiontests and modeltests into the test root.

2013-02-26T13:36:57Z