fearless_fool

Passing a value whose magnitude is less than 1.0 raises "TypeError: nil can't be coerced to fixnum":

onyx[~/Developer/bd]$ rake about
About your application's ...

(Hey - why did Lighthouse apply formatting inside of a @@@ ... @@@ block?)

The presence of backup migration files (e.g. 20110208231103_create_analysis_cdf.rb~) causes rake db:migrate:status to display spurious entries. Not a serious pr...

@SK:

The Heisenberg reference was intended to enliven your day, even if not totally accurate. But -- absent any documentation about how relations are cached -- ...

Assigning this to Aaron, since he appears to be the relationship maven. If I'm violating lighthouse etiquette by assigning the ticket, please excuse me - I'm no...

I have isolated a case where calling ActiveRecord::Relation#all (or evidently anything operation that forces evaluation) changes its state to that it subsequent...

A reason to implement @Roman Le Négrate's change is that it would allow exists?() to work on tables that lack a PK. See also ticket #615.

Doh - once again with formatting...

  > UserRole.find(:first, :conditions => {:user_id => 4, :role_id => 2})
  => #<UserRole user_id: 4, role_id: 2>

Of course...

Is there a good explanation for the wontfix status? Specifically, it is surprising that AR.exists?() fails on PK-less tables, given that AR.find() works just fi...

I'm undecided if this is a bug in ActiveRecord or a hole in the documentation, but I'm certain that it is one or the other. Consider:

irb(main):059:0> obs = Ob...