Will Bryant
Not a member
Will Bryant's latest activity
Monday, May 11 2009
-
Will Bryant commented at 2:36 AM+1 This inconsistency bugs me too. This patch works in my project and passes tests.
Wednesday, May 06 2009
-
Will Bryant commented at 4:15 AMThis is the expected current behaviour. Calling some_has_many.sum calls the Calculations module sum, which passes the string argument you give it to the databas...
Thursday, April 09 2009
-
Will Bryant commented at 3:27 AMUse :conditions => {:authors => {:name => 'BAR'}}. AFAIK :conditions => {'authors.name' => 'BAR'} has never been officially supported, though it may have worked...
Thursday, March 19 2009
-
Will Bryant commented at 3:46 AMI would prefer substituting the primary key, personally, as I feel it makes it more clear what we're doing and makes me less nervous about counts with joins (wh...
Wednesday, March 11 2009
-
Will Bryant created the ticket at 1:17 PM5cda000, which changed the autosave logic between rc1 & rc2, broke the save of any objects that have has_one :through associations :included.
The attached patch...
-
Will Bryant commented at 11:28 AMDo you know if this a regression from 2.2 or something that's never worked?
Friday, March 06 2009
-
Will Bryant created the ticket at 10:16 PMThe recently-introduced :having support isn't sanitizing the conditions, so whereas:
:having => 'sum(credit_limit) > 50'
works,
:having => ['sum(credit_limit) >...
Monday, February 16 2009
-
Will Bryant commented at 3:25 AMThe reason that I ask is that a lot of the weird stuff we do in postgres was introduced to deal with problems with the gems, and unfortunately it sticks around ...
Wednesday, February 11 2009
-
Will Bryant created the ticket at 1:55 AMArray.wrap doesn't DWIM with associations:
Array.wrap(Icp.find(16).registers) => [[#<Register ...>]]
Array.wrap(DisputedRead.unresolved) => [[#<DisputedRead ....