From 558e4e94822e922cddff315ee13db5baa67b644b Mon Sep 17 00:00:00 2001 From: Russell Keith-Magee Date: Sat, 11 Jul 2009 16:09:18 +0000 Subject: [1.0.X] Fixed #11438 -- Corrected some bad grammar in the custom fields docs. Thanks to thepointer for the report. Merge of r11220 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@11225 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/howto/custom-model-fields.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/howto/custom-model-fields.txt b/docs/howto/custom-model-fields.txt index 709ea49b87..9f798f14d5 100644 --- a/docs/howto/custom-model-fields.txt +++ b/docs/howto/custom-model-fields.txt @@ -464,7 +464,7 @@ should raise either a ``ValueError`` if the ``value`` is of the wrong sort (a list when you were expecting an object, for example) or a ``TypeError`` if your field does not support that type of lookup. For many fields, you can get by with handling the lookup types that need special handling for your field -and pass the rest of the :meth:`get_db_prep_lookup` method of the parent class. +and pass the rest to the :meth:`get_db_prep_lookup` method of the parent class. If you needed to implement ``get_db_prep_save()``, you will usually need to implement ``get_db_prep_lookup()``. If you don't, ``get_db_prep_value`` will be -- cgit v1.3