A non-abstract (abstract=False) model.
An attribute on a model; a given field usually maps directly to\na single database column.
\nSee Models.
\nA higher-order view function that provides an abstract/generic\nimplementation of a common idiom or pattern found in view development.
\nSee Class-based views.
\nModels store your application’s data.
\nSee Models.
\n“Model-template-view”; a software pattern, similar in style to MVC, but\na better description of the way Django does things.
\nSee the FAQ entry.
\nModel-view-controller; a software pattern. Django follows MVC\nto some extent.
\nA Python package – i.e. a directory of code – that contains all the\nsettings for an instance of Django. This would include database\nconfiguration, Django-specific options and application-specific\nsettings.
\nAlso known as “managed attributes”, and a feature of Python since\nversion 2.2. This is a neat way to implement attributes whose usage\nresembles attribute access, but whose implementation uses method calls.
\nSee property.
An object representing some set of rows to be fetched from the database.
\nSee Making queries.
\nA short label for something, containing only letters, numbers,\nunderscores or hyphens. They’re generally used in URLs. For\nexample, in a typical blog entry URL:
\nhttps://www.djangoproject.com/weblog/2008/apr/12/spring/\n
the last bit (spring) is the slug.
A chunk of text that acts as formatting for representing data. A\ntemplate helps to abstract the presentation of data from the data\nitself.
\nSee Templates.
\nA function responsible for rendering a page.
\n