Comments on: Ruby on Rails: SQL Server 2005 Pagination http://alexle.net/archives/292 Personal View Thu, 09 Sep 2010 16:02:11 +0000 http://wordpress.org/?v=2.5 By: Mike King http://alexle.net/archives/292#comment-248765 Mike King Thu, 26 Feb 2009 20:38:11 +0000 http://alexle.net/?p=292#comment-248765 I found one problem with the patch. The use of .id as the default order by criteria doesn't always work. For example in my work I've got a lot of legacy tables, and most don't use .id as the primary key. For instance my Personnel table has primary key personid. This results in bad sql generated when no :order by is specified in the find. And also when I use Personnel.count() it uses .id, and there's no way to specify an order in this case. A simple solution might be to use the primary key or id() in the place of .id I found one problem with the patch. The use of .id as the default order by criteria doesn’t always work. For example in my work I’ve got a lot of legacy tables, and most don’t use .id as the primary key. For instance my Personnel table has primary key personid.

This results in bad sql generated when no :order by is specified in the find. And also when I use Personnel.count() it uses .id, and there’s no way to specify an order in this case.

A simple solution might be to use the primary key or id() in the place of .id

]]>