StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PORails 4 .order() gets mangled with JOINS
primarykey
Id
17370432
data
AcceptedAnswerId
17687504
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-06-28T17:28:45.923
FavoriteCount
0
LastActivityDate
2013-07-16T21:40:49.113
LastEditDate
2013-07-16T21:09:24.423
LastEditorUserId
547970
OwnerUserId
547970
ParentId
0
PostTypeId
1
Score
6
ViewCount
7724
LastEditorDisplayName
text
Body
I'm working on upgrading an existing Rails 3.2 application to 4.0. I've run into a brick wall, though. I've got three models, Client, Site, and Contact. Sites are physical locations that belong to a client, and a client can have many sites. Contacts are people that belong to one or more sites. Thus, a client can have many contacts through sites. Clients: <pre><code>class Client < ActiveRecord::Base has_many :sites, -> { where(:sites => {:deleted => false}).order(:name => :asc) }, :dependent => :destroy has_many :contacts, -> { order(:lastname => :asc) }, :through => :sites end </code></pre> Sites: <pre><code>class Site < ActiveRecord::Base belongs_to :client has_and_belongs_to_many :contacts end </code></pre> Contacts: <pre><code>class Contact < ActiveRecord::Base has_and_belongs_to_many :sites end </code></pre> The problem is that when I use <code>Client.find(1).contacts</code>, I get a <code>ActiveRecord::StatementInvalid</code> exception: <blockquote> Mysql2::Error: Unknown column 'contacts.name' in 'order clause': SELECT <code>contacts</code>.* FROM <code>contacts</code> INNER JOIN <code>contacts_sites</code> ON <code>contacts</code>.<code>id</code> = <code>contacts_sites</code>.<code>contact_id</code> INNER JOIN <code>sites</code> ON <code>contacts_sites</code>.<code>site_id</code> = <code>sites</code>.<code>id</code> WHERE <code>sites</code>.<code>client_id</code> = 5 AND <code>sites</code>.<code>deleted</code> = 0 ORDER BY <code>contacts</code>.<code>lastname</code> ASC, <code>contacts</code>.<code>name</code> ASC </blockquote> There's the problem: I have no idea where the <code>ORDER BY ... `contacts`.`name` ASC</code> is coming from. The Contacts table does not have a name column, but Rails is trying to sort with it and I don't know where it's coming from or how to remove it. The <code>ORDER BY `contacts`.`lastname` ASC</code> is easy; it comes from the Client model. These relationships have worked flawlessly in 3.2, but now throw this exception in 4.0. UPDATE: It's been pointed out that the extra <code>ORDER BY ... `contacts`.`name` ASC</code> is coming from the first <code>has_many</code> in the Clients model. However, the intention there was to sort the Sites, not the Contacts. I tried changing it to <code>.order('sites.name' => :asc)</code> and SQL complained about there being no column named <code>sites.sites.name</code>. So, it appears that when using <code>:through =></code> with <code>has_many</code>, the order clause gets mangled. I tried removing the <code>.order()</code> and using <code>default_scope -> { order(:name => :asc) }</code> in the Sites model, but got exactly the same error as originally reported.
Tags
<ruby-on-rails><activerecord>
Title
Rails 4 .order() gets mangled with JOINS
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USMatthew Clark
UserOwnerUserId
1. USMatthew Clark
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PORails 4 .order() gets mangled with JOINS
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PORails 4 .order() gets mangled with JOINS
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.