Author: russellm Date: 2009-07-11 10:38:08 -0500 (Sat, 11 Jul 2009) New Revision: 11220
Modified: django/trunk/docs/howto/custom-model-fields.txt Log: Fixed #11438 -- Corrected some bad grammar in the custom fields docs. Thanks to thepointer for the report. Modified: django/trunk/docs/howto/custom-model-fields.txt =================================================================== --- django/trunk/docs/howto/custom-model-fields.txt 2009-07-11 15:37:38 UTC (rev 11219) +++ django/trunk/docs/howto/custom-model-fields.txt 2009-07-11 15:38:08 UTC (rev 11220) @@ -464,7 +464,7 @@ 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to django-updates@googlegroups.com To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-updates?hl=en -~----------~----~----~----~------~----~------~--~---
