Sql updating a query result set
If you can be sure that there will only be one ordering piece of data for each of the items you’re ordering, this approach should not present problems. There’s no way to specify whether ordering should be case sensitive.
With respect to case-sensitivity, Django will order results however your database backend normally orders them.
Since pickle compatibility errors can be difficult to diagnose, such as silently corrupted objects, a exists so that specialized query subclasses can reconstruct internal query state.
Each field you add to the ordering incurs a cost to your database.Each foreign key you add will implicitly include all of its default orderings as well.If a query doesn’t have an ordering specified, results are returned from the database in an unspecified order.Only aggregate expressions that reference a single field can be anonymous arguments. For example, if you were manipulating a list of blogs, you may want to determine how many entries have been made in each blog: queries may be expensive and slow, depending on the database backend you’re using.To order by a field in a different model, use the same syntax as when you are querying across model relations.