diff options
| author | Becka R <rebecca@rebecca-robbins.com> | 2016-02-11 11:27:15 -0800 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-02-11 18:27:14 -0500 |
| commit | ec16503f2b2da31e742ecce419c0cb22669964a8 (patch) | |
| tree | 2964bdb6e4fdfac0ba8232ef8002d2f64cbb04ac | |
| parent | 1d9ee181fe09a5c3784bbbf802cc522f11ff25ef (diff) | |
[1.9.x] Clarified "database column type" explanation.
Backport of cf48962b361b573e580b79839c19b640b7f304a2 from master
| -rw-r--r-- | docs/topics/db/models.txt | 3 |
1 files changed, 2 insertions, 1 deletions
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 </ref/forms/widgets>` to use when rendering a form field (e.g. ``<input type="text">``, ``<select>``). |