From d9a30ed190d68a5450cba8b3cd26ef6bcd8a70ff Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Tue, 17 Mar 2015 20:03:07 -0400 Subject: [PATCH] Updated location of database backend data_types attribute in docs. --- docs/howto/custom-model-fields.txt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/howto/custom-model-fields.txt b/docs/howto/custom-model-fields.txt index 35dfd4cb79..58c81a70f4 100644 --- a/docs/howto/custom-model-fields.txt +++ b/docs/howto/custom-model-fields.txt @@ -692,12 +692,12 @@ storing a string. 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 -``django.db.backends..creation.data_types`` -- the string will still be -used by the serializer, but the default :meth:`~Field.db_type` method will -return ``None``. See the documentation of :meth:`~Field.db_type` for reasons why -this might be useful. Putting a descriptive string in as the type of the field -for the serializer is a useful idea if you're ever going to be using the -serializer output in some other place, outside of Django. +``django.db.backends..base.DatabaseWrapper.data_types`` -- the string +will still be used by the serializer, but the default :meth:`~Field.db_type` +method will return ``None``. See the documentation of :meth:`~Field.db_type` +for reasons why this might be useful. Putting a descriptive string in as the +type of the field for the serializer is a useful idea if you're ever going to +be using the serializer output in some other place, outside of Django. .. _converting-model-field-to-serialization: