Comments on: OData Query Option top Forces Data To Be Sorted By Primary Key http://peterkellner.net/2010/03/31/odata-wcfdataservice-top-orderby-default-sort/ Microsoft Focussed, JavaScript (ExtJS, SenchaTouch & Windows 8 Metro) Wed, 08 Feb 2012 21:38:46 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: LA http://peterkellner.net/2010/03/31/odata-wcfdataservice-top-orderby-default-sort/comment-page-1/#comment-31169 LA Thu, 20 Oct 2011 22:46:46 +0000 http://peterkellner.net/2010/03/31/odata-wcfdataservice-top-orderby-default-sort/#comment-31169 So let me get this straight. If you DO NOT specify a $orderby or $top option, then the results from OData will be listed in the order the items were inserted into the database? So let me get this straight. If you DO NOT specify a $orderby or $top option, then the results from OData will be listed in the order the items were inserted into the database?

]]> By: Peter http://peterkellner.net/2010/03/31/odata-wcfdataservice-top-orderby-default-sort/comment-page-1/#comment-26363 Peter Wed, 31 Mar 2010 19:30:31 +0000 http://peterkellner.net/2010/03/31/odata-wcfdataservice-top-orderby-default-sort/#comment-26363 Hi Marcelo, The reason I did not expect the behavior is because I am use to SQL Server and how it handles Select top. In SqlServer, using select top does not force a sort. Hi Marcelo,
The reason I did not expect the behavior is because I am use to SQL Server and how it handles Select top. In SqlServer, using select top does not force a sort.

]]> By: Marcelo - MSFT http://peterkellner.net/2010/03/31/odata-wcfdataservice-top-orderby-default-sort/comment-page-1/#comment-26362 Marcelo - MSFT Wed, 31 Mar 2010 18:49:40 +0000 http://peterkellner.net/2010/03/31/odata-wcfdataservice-top-orderby-default-sort/#comment-26362 Just wanted to drop a note and confirm that this is indeed the case. The idea behind this decision is that we wanted clients to be able to 'scan' a complete feed by using a series of $top/$skip requests, but to do that we need to guarantee that the results are ordered by *something*. So if there isn't an $orderby option, the system orders by primary key (which will give a stable order to all entries). Just wanted to drop a note and confirm that this is indeed the case.

The idea behind this decision is that we wanted clients to be able to ’scan’ a complete feed by using a series of $top/$skip requests, but to do that we need to guarantee that the results are ordered by *something*.

So if there isn’t an $orderby option, the system orders by primary key (which will give a stable order to all entries).

]]>