Yes, I am running it in 1.9 mode. Our project is stuck at 1.6.5.1 for now 
until we are allowed to upgrade later...

On Thursday, July 12, 2012 12:01:41 PM UTC-7, Jeremy Evans wrote:
>
> On Thursday, July 12, 2012 11:27:13 AM UTC-7, Matt Hauck wrote:
>>
>> Okay, so it does definitely have to do with prepared statements: 
>>
>> jruby-1.6.5.1 :019 > t = Time.now
>>  => 2012-07-12 11:14:21 -0700 
>> jruby-1.6.5.1 :020 > t.to_f
>>  => 1342116861.229 
>> jruby-1.6.5.1 :021 > DB[:t].insert :a => t
>>  => 0 
>> jruby-1.6.5.1 :022 > DB['select * from t'].map {|r| r[:a].to_f }
>>  => [1342116861.229] 
>> jruby-1.6.5.1 :023 > DB[:t].call(:insert, {:t => t}, :$t)
>>  => 0 
>> jruby-1.6.5.1 :024 > DB['select * from t'].map {|r| r[:a].to_f }
>>  => [1342116861.229, 1342116861.0] 
>>
>>
> I see you are running an older version of jruby.  Are you by chance 
> running it in ruby 1.9 mode?  I believe Time#nsec has a bug in jruby 1.6 
> ruby 1.9 mode.  I worked around it in one place in Sequel, perhaps I need 
> to do so here as well.
>
> Jeremy
>

-- 
You received this message because you are subscribed to the Google Groups 
"sequel-talk" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/sequel-talk/-/qxlOHTaYWU8J.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sequel-talk?hl=en.

Reply via email to