diff options
| author | Tobias Kunze <r@rixx.de> | 2019-06-17 16:54:55 +0200 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2019-09-06 13:27:46 +0200 |
| commit | 4a954cfd11a5d034491f87fcbc920eb97a302bb3 (patch) | |
| tree | 1c92caae5d8a9b33c51ddd74b4b2061248f3915f /docs/faq/models.txt | |
| parent | addabc492bdc0191ac95d59ec34b56b34086ebb9 (diff) | |
Fixed #30573 -- Rephrased documentation to avoid words that minimise the involved difficulty.
This patch does not remove all occurrences of the words in question.
Rather, I went through all of the occurrences of the words listed
below, and judged if they a) suggested the reader had some kind of
knowledge/experience, and b) if they added anything of value (including
tone of voice, etc). I left most of the words alone. I looked at the
following words:
- simply/simple
- easy/easier/easiest
- obvious
- just
- merely
- straightforward
- ridiculous
Thanks to Carlton Gibson for guidance on how to approach this issue, and
to Tim Bell for providing the idea. But the enormous lion's share of
thanks go to Adam Johnson for his patient and helpful review.
Diffstat (limited to 'docs/faq/models.txt')
| -rw-r--r-- | docs/faq/models.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/faq/models.txt b/docs/faq/models.txt index c6a7f28e23..89bbbd1724 100644 --- a/docs/faq/models.txt +++ b/docs/faq/models.txt @@ -8,7 +8,7 @@ How can I see the raw SQL queries Django is running? ==================================================== Make sure your Django :setting:`DEBUG` setting is set to ``True``. -Then, just do this:: +Then do this:: >>> from django.db import connection >>> connection.queries @@ -32,7 +32,7 @@ same interface on each member of the ``connections`` dictionary:: >>> connections['my_db_alias'].queries If you need to clear the query list manually at any point in your functions, -just call ``reset_queries()``, like this:: +call ``reset_queries()``, like this:: from django.db import reset_queries reset_queries() @@ -61,8 +61,8 @@ But this isn't an issue in practice, because there's nothing stopping you from adding other constraints (using the ``unique_together`` model option or creating the constraint directly in your database), and enforcing the uniqueness at that level. Single-column primary keys are needed for things such -as the admin interface to work; e.g., you need a simple way of being able to -specify an object to edit or delete. +as the admin interface to work; e.g., you need a single value to specify +an object to edit or delete. Does Django support NoSQL databases? ==================================== |
