Author: kmtracey Date: 2008-11-01 14:20:00 -0500 (Sat, 01 Nov 2008) New Revision: 9314
Modified: django/trunk/docs/howto/custom-model-fields.txt Log: Fixed #9412 -- Corrected a couple of typos in the custom model field doc. Thanks carljm. Modified: django/trunk/docs/howto/custom-model-fields.txt =================================================================== --- django/trunk/docs/howto/custom-model-fields.txt 2008-11-01 19:05:46 UTC (rev 9313) +++ django/trunk/docs/howto/custom-model-fields.txt 2008-11-01 19:20:00 UTC (rev 9314) @@ -437,7 +437,7 @@ You only need to override this method if you want to preprocess the value somehow, just before saving. For example, Django's -`:class:`~django.db.models.DateTimeField` uses this method to set the attribute +:class:`~django.db.models.DateTimeField` uses this method to set the attribute correctly in the case of :attr:`~django.db.models.Field.auto_now` or :attr:`~django.db.models.Field.auto_now_add`. @@ -569,7 +569,7 @@ .. method:: value_to_string(self, obj) This method is used by the serializers to convert the field into a string for -output. Calling :meth:``Field._get_val_from_obj(obj)`` is the best way to get the +output. Calling :meth:`Field._get_val_from_obj(obj)` is the best way to get the value to serialize. For example, since our ``HandField`` uses strings for its data storage anyway, we can reuse some existing conversion code:: --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-updates?hl=en -~----------~----~----~----~------~----~------~--~---
