# in app/models/user.rb:
def not_yet_listened_recordings
ls = Listening.find_by_sql(["select distinct recording_id from
listenings where user_id=?, self.id])
return Recording.find(:all) if not ls or ls.empty?
criteria_a =
vals_a =
ls.each do |l|
criteria_a << "id<>?"
vals_a << l.recording_id.to_i
end
qstr = "select * from recordings where #{criteria_a.join(' and
')}"
sql_a = [qstr] + vals_a
return Recording.find_by_sql(sql_a)
end
I just tried this out and it's much faster (5-8x) than my method (I'm
guessing it's because it dosen't have to select * from recordings).
You could also do something like this
select recordings.* from recordings
left outer join listened_recordings on recording_id = recordings.id
and user_id = 12345
where listened_recordings.id IS NULL
rewriting that sql as something you can use is left as an exercise to
the reader
On Jeff's method, one quick optimization would be to switch to using
a NOT IN query:
# in app/models/user.rb:
def not_yet_listened_recordings
ls = Listening.find_by_sql(["select distinct recording_id from
listenings where user_id=?, self.id])
return Recording.find(:all) if not ls or ls.empty?
Recording.find(:all, :conditions => ['id NOT IN (?)', ls])
end
A lot less code for the same result...
Overall though, the Fred's LEFT OUTER JOIN thing is much more elegant;
it also lends itself to being used as a named scope - which you'll
want when
it comes time to paginate the list.
Example:
# in recording.rb:
named_scope :not_listened, lambda { |u| { :joins => "LEFT OUTER JOIN
listenings ON recording_id = recordings.id AND listener_id = #
{u.id}", :conditions => [ "recording_id IS NULL" ] } }
Then you could have a controller action (using mislav-will_paginate);
def show_not_listened
# get a user object somehow - either logged in user or from params
@recordings = Recording.not_listened(user).paginate(params[:page] ||
1)
end