Changes between Version 89 and Version 90 of BackwardsIncompatibleChanges

Timestamp:

May 8, 2007, 6:10:09 AM (17 years ago)

Author:

Malcolm Tredinnick

Comment:

Described generic relation change

BackwardsIncompatibleChanges

@@ -23 +23 @@
  * April 25, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#LOGIN_URLisnowasetting Login URL is now a setting]
  * May 5, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#TestClientloginmethodchanged Test Client `login()` method changed]
+ * May 8, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Genericrelationshavemoved Generic relations have moved]
 
 == Database constraint names changed ==
@@ -144 +145 @@
 c.login(username='myuser', password='mypassword')
 }}}
-The keyword arguments `username` and `password` *must* be given explicitly. If an alternate authentication scheme is in use, the credentials required by that scheme can be provided instead of `username` and `password`. 
+The keyword arguments `username` and `password` *must* be given explicitly. If an alternate authentication scheme is in use, the credentials required by that scheme can be provided instead of `username` and `password`.
+
+== Generic relations have moved ==
+
+In [5172], the various generic relation classes (!GenericForeignKey and !GenericRelation) have moved into the django.contrib.contenttypes module. This is because they will not work if contenttypes is not an installed app. Making the import path reflect the dependency should help remind people of this.
+
+Code using generic relations should change from saying things like
+{{{
+#!python
+generic_field = models.GenericRelation(SomeOtherModel)
+}}}
+to using
+{{{
+#!python
+from django.contrib.contenttypes import generic
+...
+generic_field = generic.GenericRelation(SomeOtherModel)
+}}}
+
+No database changes or other model changes are required.