* Michael Schoen ([EMAIL PROTECTED]) [060228 20:03]:
> Yeah, except that seems backwards -- the key actually is an int, would 
> be nice if we could leave it that way. Actually forcing it to a string 
> in calculations seems odd.
> 
> I was also thinking that it could be resolved by returning something 
> like OrderedHashWithIndifferentAccess, and having the unit tests test 
> using the symbols.

I haven't had a chance to run the new calculations code against our
Oracle install yet, but I'd believe that the Oracle adapter+driver's
"smart" typecasting is at work.

It seems like client code (which test code also is) should be oblivious
to the underlying database adapter -- so far the indifferent access
technique seems like the most straightforward way to get uniform
behavior to me.

Rick
-- 
 http://www.rickbradley.com    MUPRN: 716
                       |  absurd and annoying
   random email haiku  |  EULA everyone clicks through
                       |  without reading now).
_______________________________________________
Rails-core mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails-core

Reply via email to