diff options
| author | Timothy Allen <flipper@peregrinesalon.com> | 2016-10-31 15:22:32 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-10-31 15:22:32 -0400 |
| commit | 5595db9504ca3fe431f04f853ac8b71edac012c9 (patch) | |
| tree | 6acf789618a21ce7af420d85ef599fca18753346 | |
| parent | 2f9861d823620da7ecb291a8f005f53da12b1e89 (diff) | |
Updated docs/topics/db/queries.txt examples to use print() function.
| -rw-r--r-- | docs/topics/db/queries.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/topics/db/queries.txt b/docs/topics/db/queries.txt index b0d04a659c..ea203c4ea0 100644 --- a/docs/topics/db/queries.txt +++ b/docs/topics/db/queries.txt @@ -763,16 +763,16 @@ For example, repeatedly getting a certain index in a queryset object will query the database each time:: >>> queryset = Entry.objects.all() - >>> print queryset[5] # Queries the database - >>> print queryset[5] # Queries the database again + >>> print(queryset[5]) # Queries the database + >>> print(queryset[5]) # Queries the database again However, if the entire queryset has already been evaluated, the cache will be checked instead:: >>> queryset = Entry.objects.all() >>> [entry for entry in queryset] # Queries the database - >>> print queryset[5] # Uses cache - >>> print queryset[5] # Uses cache + >>> print(queryset[5]) # Uses cache + >>> print(queryset[5]) # Uses cache Here are some examples of other actions that will result in the entire queryset being evaluated and therefore populate the cache:: |
