Forum: Ruby on Rails query pulling too many fields

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Scott K. (Guest)
on 2009-04-17 04:58
i'm a little confused here on what's happening.

i have two tables ITEMS and ITEM_TYPES

ITEMS (belongs_to :item_type)


here is my Item.rb model code for my query:

         :select => ',',
         :include => :item_type,
         :conditions => [' = ? OR = ? OR = ? OR = ?', 'Material', 'Weapon',
'Armor', 'Accessory'],
         :order => '')

currently it is selecting all fields in the ITEM table and not using the
:select that i have entered.

if i comment out the :conditions parameter the :select works properly.
i'm sure it's something to do with the linking to the item_types table.
does anyone know how i can get the above :select working properly?

Harold (Guest)
on 2009-04-17 05:31
(Received via mailing list)
The find's :select option is ignored when you combine it with
the :include option.

On Apr 16, 8:58 pm, Scott K. <removed_email_address@domain.invalid>
Scott K. (Guest)
on 2009-04-17 05:49
Harold wrote:
> The find's :select option is ignored when you combine it with
> the :include option.
> On Apr 16, 8:58�pm, Scott K. <removed_email_address@domain.invalid>

thanks.  i removed the include and did my joins manually.  i guess
that's probably the best way:

         :select => ',,',
         :joins => 'join item_types on items.item_type_id =',
         :conditions => [' = ? OR = ? OR = ? OR = ?', 'Material', 'Weapon',
'Armor', 'Accessory'],
         :order => '')
Matt J. (Guest)
on 2009-04-19 01:36
(Received via mailing list)
The whole operation smells like a somewhat premature operation, unless
either Item or ItemType has a whole bunch of fields you didn't
mention. Why not just let AR work the way it does?

Item.find(:all, :include => :item_type, :conditions =>
{ :'' => %w(Material Weapon Armor Accessory) })

(that last bit changes the chain of 'OR's above into an IN statement,
which is a cheap optimization, and easier to change later...)

--Matt J.

On Apr 16, 9:49 pm, Scott K. <removed_email_address@domain.invalid>
This topic is locked and can not be replied to.