diff options
| author | Claude Paroz <claude@2xlibre.net> | 2016-09-02 20:17:15 +0200 |
|---|---|---|
| committer | Claude Paroz <claude@2xlibre.net> | 2016-09-03 13:46:41 +0200 |
| commit | 2ced2f785d5aca0354abf5841d5449b7a49509dc (patch) | |
| tree | 46ade22a7c8d9ccdbab4a7fcb25f702172352521 /docs/ref/databases.txt | |
| parent | b1d6b0a7b121eec860b518b4903d7c8c74f7773b (diff) | |
Replaced smart_* by force_* calls whenever possible
The smart_* version should only be used when a lazy string should keep
its lazy status.
Diffstat (limited to 'docs/ref/databases.txt')
| -rw-r--r-- | docs/ref/databases.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index 6d705beb66..6412316a2d 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -369,7 +369,7 @@ to you, the developer, to handle the fact that you will receive bytestrings if you configure your table(s) to use ``utf8_bin`` collation. Django itself should mostly work smoothly with such columns (except for the ``contrib.sessions`` ``Session`` and ``contrib.admin`` ``LogEntry`` tables described below), but -your code must be prepared to call ``django.utils.encoding.smart_text()`` at +your code must be prepared to call ``django.utils.encoding.force_text()`` at times if it really wants to work with consistent data -- Django will not do this for you (the database backend layer and the model population layer are separated internally so the database layer doesn't know it needs to make this |