Joshua White

The has_many :through breaks when the models aren't all in the same db using establish_connection. I saw there were some updates in rails 2.3.4 so I updated to ...

Does this mean that the ability to not include the nil=>'true' is left to the individual to do themselves? Should I submit a patch? I am for adding a skip_nils ...

I did the same thing on 4 of my rails sites and they all seem fine. Does mean we need to submit a patch?

I found a workaround, it took me installing rails local gems, then I had to modify the file...

rack-1.0.0/lib/rack/handler/fastcgi.rb
And comment out the alias ...

I am hosting on Bluehost who just cowboyed through a update to 2.3.2, then the next day to 2.3.3. I got everything working fine in 2.3.2, but the 2.3.3 is just ...

I wrote the exact same sort of thing a few months back. There was a bit of discussion and I talked with Eloy a bit as well.

My patch added two options, each app...

Sorry, I realized my last post was incorrect, it was comparing exam_record.id to history.patient_id, and that this bug is closed, I just had to specify the prim...

I tried a number of things and eventually realized I could just specify the foreign_key
so in my
History.rb
belongs_to :patient

Patient.rb
has_many :exam_record...

Is there a good way to do this in the case that the join model is a has_one relationship? Or is writing SQL the best way to do it?

Apparently this is discussed in #1149, the has_one through only works when the join is a has_many or belongs_to.