mirror of
https://github.com/django/django.git
synced 2025-10-09 23:09:12 +00:00
[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
This commit is contained in:
parent
5c2518539c
commit
558e4e9482
@ -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
|
||||
|
Loading…
x
Reference in New Issue
Block a user