On Feb 25, 3:14 pm, Jason Thomas wrote:
> I'm using data that I always want converted to floats not BigDecimal.
> I'm not inheriting from Sequel::Model so I can't really force the
> issue there. Is there an easy way (monkey patch) that can convert
> BigDecimal to float for every returned value?
N
On 2/25/11 3:25 PM, Jason Thomas wrote:
> My experience would be to recommend AR first. Especially if you're
> going to try to use testing tools like Cucumber and such. They are all
> geared toward AR first, then maybe DataMapper or Mongo. Sequel require
> you to do some message board posting/searc
My experience would be to recommend AR first. Especially if you're
going to try to use testing tools like Cucumber and such. They are all
geared toward AR first, then maybe DataMapper or Mongo. Sequel require
you to do some message board posting/searching (which Jeremy
diligently responds to) but u
On Feb 25, 2:37 pm, Kedar Mhaswade wrote:
> I have been teaching Ruby and Ruby on Rails to myself. I ran into
> geonames processing and then came to know of Sequel and it looks cool.
> Some search also reveals that it has very good performance
> characteristics. But then I am unsure of whether I s
I'm using data that I always want converted to floats not BigDecimal.
I'm not inheriting from Sequel::Model so I can't really force the
issue there. Is there an easy way (monkey patch) that can convert
BigDecimal to float for every returned value?
--
You received this message because you are subs
I have been teaching Ruby and Ruby on Rails to myself. I ran into
geonames processing and then came to know of Sequel and it looks cool.
Some search also reveals that it has very good performance
characteristics. But then I am unsure of whether I should learn/use
Sequel instead of activerecord for
