Changes between Version 140 and Version 141 of BackwardsIncompatibleChanges

Timestamp:

Dec 11, 2007, 11:06:29 PM (16 years ago)

Author:

Gary Wilson

Comment:

noted MultipleObjectsReturned change

BackwardsIncompatibleChanges

@@ -47 +47 @@
  * [6832] Dec 2, 2007: [#Settingsexceptiontypeschanged Settings exception types changed]
  * [6833] Dec 2, 2007: [#Genericviewsemptydefaults Generic views' empty defaults]
+ * [6838] Dec. 3, 2007: [#MultipleObjectsReturnedexceptioninsteadofAssertionError MultipleObjectsReturned exception instead of AssertionError]
 
 == Database constraint names changed ==
@@ -485 +486 @@
 
 In [6833] the {{{allow_empty}}} parameter to the {{{archive_index()}}} and {{{object_list()}}} generic views were changed to be True by default. So viewing a list of objects that is empty will not raise a 404 HTTP error. Things like date-based views still raise a 404 when there is nothing to view (by default), since viewing a non-existent date is usually going to be an error. See #685 for details.
+
+
+== `MultipleObjectsReturned` exception instead of `AssertionError` ==
+
+In [6838], `QuerySet.get()` was changed to raise a `MultipleObjectsReturned` exception rather than an assertion error when multiple objects are returned.
+
+Before:
+{{{
+#!python
+try:
+    Model.objects.get(...)
+except AssertionError:
+    ...
+}}}
+
+After:
+{{{
+#!python
+try:
+    Model.objects.get(...)
+except Model.MultipleObjectsReturned:
+    ...
+}}}