ordering. For example, if the default ordering is by a non-unique name field, then the changelist is sorted by name and pk. This could perform poorly if you have a lot of rows and don’t have an index on name default. Collation settings The collation setting for a column controls the order in which data is sorted as well as what strings compare as equal. It can be set on a database-wide level and also per- table desc()) asc() and desc() have arguments (nulls_first and nulls_last) that control how null values are sorted. Be cautious when ordering by fields in related models if you are also using distinct(). See the

ordering. For example, if the default ordering is by a non-unique name field, then the changelist is sorted by name and pk. This could perform poorly if you have a lot of rows and don’t have an index on name default. Collation settings The collation setting for a column controls the order in which data is sorted as well as what strings compare as equal. It can be set on a database-wide level and also per- table desc()) asc() and desc() have arguments (nulls_first and nulls_last) that control how null values are sorted. Be cautious when ordering by fields in related models if you are also using distinct(). See the

ordering. For example, if the default ordering is by a non-unique name field, then the changelist is sorted by name and pk. This could perform poorly if you have a lot of rows and don’t have an index on name for the model add_url: admin URL to add a new model instance Lists of applications and models are sorted alphabetically by their names. You can override this method to change the default order on the admin default. Collation settings The collation setting for a column controls the order in which data is sorted as well as what strings compare as equal. You can specify the db_collation parameter to set the

ordering. For example, if the default ordering is by a non-unique name field, then the changelist is sorted by name and pk. This could perform poorly if you have a lot of rows and don’t have an index on name for the model add_url: admin URL to add a new model instance Lists of applications and models are sorted alphabetically by their names. You can override this method to change the default order on the admin default. Collation settings The collation setting for a column controls the order in which data is sorted as well as what strings compare as equal. You can specify the db_collation parameter to set the collation

ordering. For example, if the default ordering is by a non-unique name field, then the changelist is sorted by name and pk. This could perform poorly if you have a lot of rows and don’t have an index on name default. Collation settings The collation setting for a column controls the order in which data is sorted as well as what strings compare as equal. It can be set on a database-wide level and also per-table desc()) asc() and desc() have arguments (nulls_first and nulls_last) that control how null values are sorted. Be cautious when ordering by fields in related models if you are also using distinct(). See the

ordering. For example, if the default ordering is by a non-unique name field, then the changelist is sorted by name and pk. This could perform poorly if you have a lot of rows and don’t have an index on name default. Collation settings The collation setting for a column controls the order in which data is sorted as well as what strings compare as equal. You can specify the db_collation parameter to set the collation desc()) asc() and desc() have arguments (nulls_first and nulls_last) that control how null values are sorted. Be cautious when ordering by fields in related models if you are also using distinct(). See the

ordering. For example, if the default ordering is by a non-unique name field, then the changelist is sorted by name and pk. This could perform poorly if you have a lot of rows and don’t have an index on name default. Collation settings The collation setting for a column controls the order in which data is sorted as well as what strings compare as equal. You can specify the db_collation parameter to set the collation desc()) asc() and desc() have arguments (nulls_first and nulls_last) that control how null values are sorted. Be cautious when ordering by fields in related models if you are also using distinct(). See the

ordering. For example, if the default ordering is by a non-unique name field, then the changelist is sorted by name and pk. This could perform poorly if you have a lot of rows and don’t have an index on name default. Collation settings The collation setting for a column controls the order in which data is sorted as well as what strings compare as equal. It can be set on a database-wide level and also per-table desc()) asc() and desc() have arguments (nulls_first and nulls_last) that control how null values are sorted. Be cautious when ordering by fields in related models if you are also using distinct(). See the

ordering. For example, if the default ordering is by a non-unique name field, then the changelist is sorted by name and pk. This could perform poorly if you have a lot of rows and don’t have an index on name default. Collation settings The collation setting for a column controls the order in which data is sorted as well as what strings compare as equal. You can specify the db_collation parameter to set the collation desc()) asc() and desc() have arguments (nulls_first and nulls_last) that control how null values are sorted. Be cautious when ordering by fields in related models if you are also using distinct(). See the

ordering. For example, if the default ordering is by a non-unique name field, then the changelist is sorted by name and pk. This could perform poorly if you have a lot of rows and don’t have an index on name default. Collation settings The collation setting for a column controls the order in which data is sorted as well as what strings compare as equal. You can specify the db_collation parameter to set the collation desc()) asc() and desc() have arguments (nulls_first and nulls_last) that control how null values are sorted. Be cautious when ordering by fields in related models if you are also using distinct(). See the