innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

[1.8.x] Updated location of database backend data_types attribute in docs. 

Backport of d9a30ed190 from master
This commit is contained in:
Tim Graham 2015-03-17 20:03:07 -04:00
parent 0c92913bb0
commit 4cc501205d
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -701,12 +701,12 @@ storing a string.
If :meth:`.get_internal_type` returns a string that is not known to Django for If :meth:`.get_internal_type` returns a string that is not known to Django for
the database backend you are using -- that is, it doesn't appear in the database backend you are using -- that is, it doesn't appear in
``django.db.backends.<db_name>.creation.data_types`` -- the string will still be ``django.db.backends.<db_name>.base.DatabaseWrapper.data_types`` -- the string
used by the serializer, but the default :meth:`~Field.db_type` method will will still be used by the serializer, but the default :meth:`~Field.db_type`
return ``None``. See the documentation of :meth:`~Field.db_type` for reasons why method will return ``None``. See the documentation of :meth:`~Field.db_type`
this might be useful. Putting a descriptive string in as the type of the field for reasons why this might be useful. Putting a descriptive string in as the
for the serializer is a useful idea if you're ever going to be using the type of the field for the serializer is a useful idea if you're ever going to
serializer output in some other place, outside of Django. be using the serializer output in some other place, outside of Django.
.. _converting-model-field-to-serialization: .. _converting-model-field-to-serialization: