Loading docs/ref/templates/builtins.txt +24 −10 Original line number Diff line number Diff line Loading @@ -833,12 +833,17 @@ This complex tag is best illustrated by way of an example: say that "places" is ...and you'd like to display a hierarchical list that is ordered by country, like this: * India * Mumbai: 19,000,000 * Calcutta: 15,000,000 * USA * New York: 20,000,000 * Chicago: 7,000,000 * Japan * Tokyo: 33,000,000 Loading Loading @@ -893,14 +898,23 @@ With this input for ``cities``, the example ``{% regroup %}`` template code above would result in the following output: * India * Mumbai: 19,000,000 * USA * New York: 20,000,000 * India * Calcutta: 15,000,000 * USA * Chicago: 7,000,000 * Japan * Tokyo: 33,000,000 The easiest solution to this gotcha is to make sure in your view code that the Loading docs/releases/1.6.txt +5 −5 Original line number Diff line number Diff line Loading @@ -836,8 +836,8 @@ Object Relational Mapper changes Django 1.6 contains many changes to the ORM. These changes fall mostly in three categories: 1. Bug fixes (e.g. proper join clauses for generic relations, query combining, join promotion, and join trimming fixes) 1. Bug fixes (e.g. proper join clauses for generic relations, query combining, join promotion, and join trimming fixes) 2. Preparation for new features. For example the ORM is now internally ready for multicolumn foreign keys. 3. General cleanup. Loading docs/topics/cache.txt +6 −5 Original line number Diff line number Diff line Loading @@ -171,9 +171,10 @@ To use a database table as your cache backend: * Set :setting:`BACKEND <CACHES-BACKEND>` to ``django.core.cache.backends.db.DatabaseCache`` * Set :setting:`LOCATION <CACHES-LOCATION>` to ``tablename``, the name of the database table. This name can be whatever you want, as long as it's a valid table name that's not already being used in your database. * Set :setting:`LOCATION <CACHES-LOCATION>` to ``tablename``, the name of the database table. This name can be whatever you want, as long as it's a valid table name that's not already being used in your database. In this example, the cache table's name is ``my_cache_table``:: Loading docs/topics/forms/index.txt +3 −3 File changed.Contains only whitespace changes. Show changes Loading
docs/ref/templates/builtins.txt +24 −10 Original line number Diff line number Diff line Loading @@ -833,12 +833,17 @@ This complex tag is best illustrated by way of an example: say that "places" is ...and you'd like to display a hierarchical list that is ordered by country, like this: * India * Mumbai: 19,000,000 * Calcutta: 15,000,000 * USA * New York: 20,000,000 * Chicago: 7,000,000 * Japan * Tokyo: 33,000,000 Loading Loading @@ -893,14 +898,23 @@ With this input for ``cities``, the example ``{% regroup %}`` template code above would result in the following output: * India * Mumbai: 19,000,000 * USA * New York: 20,000,000 * India * Calcutta: 15,000,000 * USA * Chicago: 7,000,000 * Japan * Tokyo: 33,000,000 The easiest solution to this gotcha is to make sure in your view code that the Loading
docs/releases/1.6.txt +5 −5 Original line number Diff line number Diff line Loading @@ -836,8 +836,8 @@ Object Relational Mapper changes Django 1.6 contains many changes to the ORM. These changes fall mostly in three categories: 1. Bug fixes (e.g. proper join clauses for generic relations, query combining, join promotion, and join trimming fixes) 1. Bug fixes (e.g. proper join clauses for generic relations, query combining, join promotion, and join trimming fixes) 2. Preparation for new features. For example the ORM is now internally ready for multicolumn foreign keys. 3. General cleanup. Loading
docs/topics/cache.txt +6 −5 Original line number Diff line number Diff line Loading @@ -171,9 +171,10 @@ To use a database table as your cache backend: * Set :setting:`BACKEND <CACHES-BACKEND>` to ``django.core.cache.backends.db.DatabaseCache`` * Set :setting:`LOCATION <CACHES-LOCATION>` to ``tablename``, the name of the database table. This name can be whatever you want, as long as it's a valid table name that's not already being used in your database. * Set :setting:`LOCATION <CACHES-LOCATION>` to ``tablename``, the name of the database table. This name can be whatever you want, as long as it's a valid table name that's not already being used in your database. In this example, the cache table's name is ``my_cache_table``:: Loading