sql-order-by

My table (SQL Server 2008) has 1 million+ records, when I try to order records by datetime, it takes 1 second, but when I order by ID (int), it only takes about 0.1 second. Is there any way to improve the efficiency? (I already added the datetime column to the index) Ordering by id probably uses a clustered index scan while ordering by datetime uses either sorting or index lookup. Both these methods are more slow than a clustered index scan. If your table is clustered by id , basically it means it is already sorted. The records are contained in a B+Tree which has a linked list linking the

I have been trying to find something about this topic and I can't seem to find anything, there were a few questions on here but they didn't work for my particular project. I asked a similar question about updating the table but its not going to work for what I actually want here is the list of result. -------------------------------------------------------- |id | hometeam |goalsfor|goalsagainst| awayteam | -------------------------------------------------------- | 1 |Inter Milan | 3 | 1 | FC Barcelona | -------------------------------------------------------- | 2 |FC Barcelona | 1 | 0 | Inter

The ORDER BY clause is decribed in the PostgreSQLdocumentation as: ORDER BY expression [ ASC | DESC | USING operator ] [ NULLS { FIRST | LAST } ] [, ...] Can someone give me some examples how to use the USING operator ? Is it possible to get an alternating order of the resultset? A.H. A very simple example would be: > SELECT * FROM tab ORDER BY col USING < But this is boring, because this is nothing you can't get with the traditional ORDER BY col ASC . Also the standard catalog doesn't mention anything exciting about strange comparison functions/operators. You can get a list of them: > SELECT

I have a model: class MyModel(models.Model): creation_date = models.DateTimeField(auto_now_add = True, editable=False) class Meta: get_latest_by = 'creation_date' I had a query in my view that did the following: instances = MyModel.objects.all().order_by('creation_date') And then later I wanted instances.latest() , but it would not give me the correct instance, in fact it gave me the first instance. Only when I set order_by to -creation_date or actually removed the order_by from the query did .latest() give me the correct instance. This also happens when I test this manually using python

Is there a way to get a list ordered by two fields, say last and first names? I know .listOrderByLastAndFirst and .list(sort:'last, first') won't work. Hates_ This old solution no longer works. Please see mattlary's answer below You may have to write a custom finder in HQL or use the Criteria Builder. MyDomain.find("from Domain as d order by last,first desc") Or def c = MyDomain.createCriteria() def results = c.list { order("last,first", "desc") } mattlary Hates_ criteria answer didn't seem to work for me; putting "last,first" in order will only cause exceptions saying, "Property 'last,first'

This question already has an answer here: How to use SQL Order By statement to sort results case insensitive? 3 answers All I want to do is grab the stuff in alphabetical order and ignore the capital letters. db.rawQuery("SELECT " + catName + " FROM "+tableName+" ORDER BY "+catName+" ASC COLLATE NOCASE;", null); This is the code I'm using above, but it always gives me an SQLite exception saying that COLLATE is a syntax error. android.database.sqlite.SQLiteException: near "COLLATE": syntax error: , while compiling: SELECT Artist FROM testTable COLLATE NOCASE ASC COLLATE goes before the order

I am working on a plsql procedure where i am using an insert-select statement. I need to insert into the table in ordered manner. but the order by i used in the select sql is not working. is there any specific way in oracle to insert rows in orderly fashion? The typical use case for an ordered insert is in order to co-locate particular value in the same blocks (effectively reducing the clustering factor on indexes on columns by which you have ordered the data). This generally requires a direct path insert ... insert /*+ append */ into ... select ... from ... order by ... There's nothing