From cac9b38b1a8d79bb962a4412e0d3649650d9e867 Mon Sep 17 00:00:00 2001 From: Alex Gaynor Date: Tue, 22 Dec 2009 14:37:09 +0000 Subject: [PATCH] [soc2009/multidb] Cleaned up documentation for now stale using argument. Patch from Russell Keith-Magee. git-svn-id: http://code.djangoproject.com/svn/django/branches/soc2009/multidb@11946 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/contrib/contenttypes.txt | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/docs/ref/contrib/contenttypes.txt b/docs/ref/contrib/contenttypes.txt index eadca778ff..8a926afc97 100644 --- a/docs/ref/contrib/contenttypes.txt +++ b/docs/ref/contrib/contenttypes.txt @@ -183,16 +183,12 @@ The ``ContentTypeManager`` probably won't ever need to call this method yourself; Django will call it automatically when it's needed. - .. method:: models.ContentTypeManager.get_for_model(model, using=DEFAULT_DB_ALIAS) + .. method:: models.ContentTypeManager.get_for_model(model) Takes either a model class or an instance of a model, and returns the :class:`~django.contrib.contenttypes.models.ContentType` instance representing that model. - By default, this will find the content type on the default database. - You can load an instance from a different database by providing - a ``using`` argument. - The :meth:`~models.ContentTypeManager.get_for_model()` method is especially useful when you know you need to work with a :class:`ContentType ` but don't want to go to the trouble of obtaining the model's metadata to perform a manual lookup::