Arthur de Jong

Open Source / Free Software developer

summaryrefslogtreecommitdiffstats
path: root/tests/one_to_one
Commit message (Collapse)AuthorAgeFilesLines
* Fixed #25550 -- Deprecated direct assignment to the ↵Tim Graham2015-10-271-1/+1
| | | | reverse side of a related set.
* Fixed #14368 -- Allowed setting a reverse OneToOne ↵Tim Graham2015-10-091-0/+16
| | | | relation to None.
* Fixed #25296 -- Prevented model related object cache ↵Raphael Merx2015-09-201-0/+5
| | | | pollution when create() fails due to an unsaved object.
* Fixed #25160 (again) -- Moved data loss check on reverse ↵Aymeric Augustin2015-09-191-5/+7
| | | | | | | | relations. Moved data loss check when assigning to a reverse one-to-one relation on an unsaved instance to Model.save(). This is exactly the same change as e4b813c but for reverse relations.
* Fixed #24951 -- Fixed AssertionError in delete queries ↵Tim Graham2015-08-202-2/+10
| | | | | | involving a foreign/primary key. Thanks Anssi Kääriäinen for help.
* Fixed #25160 -- Moved unsaved model instance data loss ↵Tim Graham2015-08-101-36/+13
| | | | | | | | | check to Model.save() This mostly reverts 5643a3b51be338196d0b292d5626ad43648448d3 and 81e1a35c364e5353d2bf99368ad30a4184fbb653. Thanks Carl Meyer for review.
* Fixed #21127 -- Started deprecation toward requiring ↵Flavio Curella2015-07-282-12/+12
| | | | on_delete for ForeignKey/OneToOneField
* Fixed #23791 -- Corrected object type check for pk__in=qsAnssi Kääriäinen2015-06-291-0/+18
| | | | | | | | | | | | When the pk was a relation field, qs.filter(pk__in=qs) didn't work. In addition, fixed Restaurant.objects.filter(place=restaurant_instance), where place is an OneToOneField and the primary key of Restaurant. A big thank you to Josh for review and to Tim for review and cosmetic edits. Thanks to Beauhurst for commissioning the work on this ticket.
* Fixed #24578 -- Fixed crash with QuerySet.update() on FK ↵Tim Graham2015-04-091-0/+11
| | | | | | to O2O fields. Thanks Anssi Kääriäinen for review.
* Renamed Field.rel attribute to remote_fieldAnssi Kääriäinen2015-03-251-2/+2
| | | | | | | | Field.rel is now deprecated. Rel objects have now also remote_field attribute. This means that self == self.remote_field.remote_field. In addition, made the Rel objects a bit more like Field objects. Still, marked ManyToManyFields as null=True.
* Fixed #24495 -- Allowed unsaved model instance ↵Karl Hobley2015-03-191-1/+26
| | | | assignment check to be bypassed.
* Sorted imports with isort; refs #23860.Tim Graham2015-02-061-3/+5
|
* Fixed #21414 -- Removed RelatedObject and deprecated ↵Anssi Kääriäinen2014-12-231-1/+1
| | | | Field.related.
* Fixed and restored assertions in ↵Adam Alton2014-11-251-4/+7
| | | | | | | | | OneToOneTests.test_foreign_key. These assertions had been removed in 34ba86706f and 7fe554b2a3, seemingly because they were referencing the wrong objects, and so they started failing when the checking of object types (as well as PK values) was introduced.
* Fixed #23620 -- Used more specific assertions in the ↵Berker Peksag2014-11-031-6/+6
| | | | Django test suite.
* Fixed flake8 warnings.Tim Graham2014-09-241-0/+1
|
* Removed numbering from the models.py header of some test ↵Loic Bistuer2014-09-241-1/+1
| | | | | | packages. This is a reliqua from the early days of the modeltests/regressiontests era.
* Fixed #23550 -- Normalized get_queryset() of ↵Loic Bistuer2014-09-232-1/+78
| | | | | | | | | | | | | | RelatedObjectDescriptor and ReverseSingleRelatedObjectDescriptor so they actually return QuerySet instances. Also ensured that SingleRelatedObjectDescriptor.get_queryset() accounts for use_for_related_fields=True. This cleanup lays the groundwork for #23533. Thanks Anssi Kääriäinen for the review.
* Merged one_to_one_regress into the one_to_one test package.Loic Bistuer2014-09-222-24/+297
|
* Fixed #14334 -- Query relation lookups now check object ↵Anubhav Joshi2014-07-011-1/+0
| | | | | | | types. Thanks rpbarlow for the suggestion; and loic, akaariai, and jorgecarleitao for reviews.
* Fixed #10811 -- Made assigning unsaved objects to FK, ↵Anubhav Joshi2014-06-052-1/+22
| | | | | | | | O2O, and GFK raise ValueError. This prevents silent data loss. Thanks Aymeric Augustin for the initial patch and Loic Bistuer for the review.
* Fixed #21563 -- Single related object descriptors should ↵Simon Charette2013-12-111-0/+4
| | | | | | work with `hasattr`. Thanks to Aymeric Augustin for the review and Trac alias monkut for the report.
* Fixing E302 ErrorsJason Myers2013-11-032-2/+8
| | | | Signed-off-by: Jason Myers <jason@jasonamyers.com>
* Fixed #21298 -- Fixed E301 pep8 warningsAlasdair Nicol2013-10-231-0/+1
|
* Fixed #21134 -- Prevented queries in broken transactions.Aymeric Augustin2013-09-301-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Squashed commit of the following: commit 63ddb271a44df389b2c302e421fc17b7f0529755 Author: Aymeric Augustin <aymeric.augustin@m4x.org> Date: Sun Sep 29 22:51:00 2013 +0200 Clarified interactions between atomic and exceptions. commit 2899ec299228217c876ba3aa4024e523a41c8504 Author: Aymeric Augustin <aymeric.augustin@m4x.org> 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 <aymeric.augustin@m4x.org> 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 <aymeric.augustin@m4x.org> 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 <aymeric.augustin@m4x.org> 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.
* Fixed #20895 -- Made check management command warn if a ↵Alasdair Nicol2013-08-161-2/+2
| | | | | | | BooleanField does not have a default value Thanks to Collin Anderson for the suggestion and Tim Graham for reviewing the patch.
* Removed most of absolute_import importsClaude Paroz2013-07-291-1/+1
| | | | | Should be unneeded with Python 2.7 and up. Added some unicode_literals along the way.
* Fixed #17582 - Added message to DoesNotExist exceptions.Tim Graham2013-05-271-1/+2
| | | | | Thanks simon@ for the suggestion and JordanPowell for the initial patch.
* Merged regressiontests and modeltests into the test root.Florian Apolloner2013-02-263-0/+177