From ec16503f2b2da31e742ecce419c0cb22669964a8 Mon Sep 17 00:00:00 2001 From: Becka R Date: Thu, 11 Feb 2016 11:27:15 -0800 Subject: [PATCH] [1.9.x] Clarified "database column type" explanation. Backport of cf48962b361b573e580b79839c19b640b7f304a2 from master --- docs/topics/db/models.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt index e2cc998e8b..3192e0a27f 100644 --- a/docs/topics/db/models.txt +++ b/docs/topics/db/models.txt @@ -111,7 +111,8 @@ Each field in your model should be an instance of the appropriate :class:`~django.db.models.Field` class. Django uses the field class types to determine a few things: -* The database column type (e.g. ``INTEGER``, ``VARCHAR``). +* The column type, which tells the database what kind of data to store (e.g. + ``INTEGER``, ``VARCHAR``, ``TEXT``). * The default HTML :doc:`widget ` to use when rendering a form field (e.g. ````, ``