ct_fk_field The name of the integer field that represents the ID of the related object. Defaults to object_id.

ManyToManyField.db_table The name of the table to create for storing the many-to-many data. If this is not provided, Django will assume a default name based upon the names of: the table for the model defining the relationship and the name of the field itself.

defer(*fields) In some complex data-modeling situations, your models might contain a lot of fields, some of which could contain a lot of data (for example, text fields), or require expensive processing to convert them to Python objects. If you are using the results of a queryset in some situation where you don’t know if you need those particular fields when you initially fetch the data, you can tell Django not to retrieve them from the database. This is done by passing the names of the field

DiscoverRunner.test_runner This is the class of the low-level test runner which is used to execute the individual tests and format the results. By default it is set to unittest.TextTestRunner. Despite the unfortunate similarity in naming conventions, this is not the same type of class as DiscoverRunner, which covers a broader set of responsibilities. You can override this attribute to modify the way tests are run and reported.

class DurationField(**kwargs) [source] Default widget: TextInput Empty value: None Normalizes to: A Python timedelta. Validates that the given value is a string which can be converted into a timedelta. Error message keys: required, invalid. Accepts any format understood by parse_duration().

deactivate_all() [source] Makes the active translation object a NullTranslations() instance. This is useful when we want delayed translations to appear as the original string for some reason.

class GeoQuerySet(model=None)

clean() New in Django 1.10. Normalizes the username by calling normalize_username(). If you override this method, be sure to call super() to retain the normalization.

PostgreSQL has a number of features which are not shared by the other databases Django supports. This optional module contains model fields and form fields for a number of PostgreSQL specific data types. Psycopg2 2.5 or higher is required, though we highly recommend using the latest release. Some fields require higher versions. Note Django is, and will continue to be, a database-agnostic web framework. We would encourage those writing reusable applications for the Django community to write dat

LogEntry.content_type The ContentType of the modified object.