p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

[1.0.X] Fixed #9412 -- Corrected a couple of typos in the custom model field doc. Thanks carljm. 

[9314] from trunk.


git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9315 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Karen Tracey 2008-11-01 19:21:46 +00:00
parent d6a1e2ef7a
commit fbf32bd000
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/howto/custom-model-fields.txt
View File

@ -437,7 +437,7 @@ for the first time, the ``add`` parameter will be ``True``, otherwise it will be
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 @@ Converting field data for serialization
.. 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::