summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMariusz Felisiak <felisiak.mariusz@gmail.com>2019-02-25 20:05:31 +0100
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2019-02-25 20:08:11 +0100
commit62f28f37bff299c533a614446fb2a4a58199f2a4 (patch)
tree386c4faee7f10023e32c347030cd106b4f535dee
parent370a145996ca4749abaa528079a672fd10b9632e (diff)
[2.2.x] Fixed documentation of database representation for ManyToManyField.
Backport of b0799f5d86b6c0ccb1dcba6e0d2eee336f7f5928 from master
-rw-r--r--docs/ref/models/fields.txt7
1 files changed, 3 insertions, 4 deletions
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
index 2d95233351..486247d80e 100644
--- a/docs/ref/models/fields.txt
+++ b/docs/ref/models/fields.txt
@@ -1478,10 +1478,9 @@ Behind the scenes, Django creates an intermediary join table to represent the
many-to-many relationship. By default, this table name is generated using the
name of the many-to-many field and the name of the table for the model that
contains it. Since some databases don't support table names above a certain
-length, these table names will be automatically truncated to 64 characters and a
-uniqueness hash will be used. This means you might see table names like
-``author_books_9cdf4``; this is perfectly normal. You can manually provide the
-name of the join table using the :attr:`~ManyToManyField.db_table` option.
+length, these table names will be automatically truncated and a uniqueness hash
+will be used, e.g. ``author_books_9cdf``. You can manually provide the name of
+the join table using the :attr:`~ManyToManyField.db_table` option.
.. _manytomany-arguments: