| 50 | | As you can see, this URLconf defines a few options in ``info_dict``. ``'model'`` |
|---|
| 51 | | tells the generic view which model to use (``Entry``, in this case), as well as |
|---|
| 52 | | some extra information. |
|---|
| | 50 | As you can see, this URLconf defines a few options in ``info_dict``. |
|---|
| | 51 | ``'queryset'`` tells the generic view which objects to use (all of the |
|---|
| | 52 | ``Entry`` objects, in this case), as well as some extra information (it is |
|---|
| | 53 | used by the view to determine the model being used, for example). |
|---|
| 58 | | ``model``, ``date_field``, etc.). |
|---|
| 59 | | |
|---|
| 60 | | Most generic views require the ``model`` key, which is your model class (*not* |
|---|
| 61 | | an instance of the class). |
|---|
| | 59 | ``queryset``, ``date_field``, etc.). |
|---|
| | 60 | |
|---|
| | 61 | Most generic views require the ``queryset`` key, which is a ``QuerySet`` |
|---|
| | 62 | instance (*not* an instance of the class); see the `database API docs`_ |
|---|
| | 63 | for more information about query sets. |
|---|