hi,

I just found this thread because I had a similar problem. I don't think 
it has something to do with drb, in fact my problem was that a "find" on 
an activerecord returned a nil object. Here is the gotcha : nil is still 
an object and has an id ... which has nothing to do with database id's. 
As ruby's author knows it's an usual pitfall, calling that method 
produces a warning.

I think the alias workaround is great, here is the syntax I used :

class ActiveRecord::Base
  alias_method :id__, :id
end

This way you can use the method id__ for any ActiveRecord::Base 
descendant. Useful to spot some bugs !

-- 
Posted via http://www.ruby-forum.com/.