ansaurus

Question

Answer 1

A:

What is your system date? from console:

date

Tombart 2010-09-10 07:53:55

what command do I type?

Brian 2010-09-10 08:00:57

what OS are you on?

ormuriauga 2010-09-10 08:15:57

I am using windows 7

Brian 2010-09-10 08:17:34

then you can just check the system clock (I think it is in the bottom right corner)

ormuriauga 2010-09-10 08:20:19

Answer 2

A:

created_at < 10.minutes.ago should work

ormuriauga 2010-09-10 07:55:21

that doesn't seem to work.. If I just create the object and type 1 minute ago after 2 it still says true

Brian 2010-09-10 08:05:37

try appending to_date and see it that helps `created_at < 10.minutes.ago.to_date`

ormuriauga 2010-09-10 08:15:36

Is your database server on the same machine as the running code?

ormuriauga 2010-09-10 08:16:30

no its not.. just testing out the app on my desktop

Brian 2010-09-10 08:17:57

so there is probably a mismatch on your date settings. try to fix that

ormuriauga 2010-09-10 08:19:11

what time do you get if you print `created_at` from a newly created object? and what time do you have on your machine?

ormuriauga 2010-09-10 08:19:49

created_at is Fri, 10 Sep 2010 06:26:22 UTC +00:00

Brian 2010-09-10 08:26:34

my machine is todays date at 3:26

Brian 2010-09-10 08:27:03

this seems to work.. u.online.created_at > u.online.create_at - 10.minutes

Brian 2010-09-10 08:37:15

but that will always be true.

ormuriauga 2010-09-10 08:40:00

lol yeah I just thought of that

Brian 2010-09-10 08:43:05

your problem, I think, is that your database is in another timezone. you need to compensate for that `u.online.created_at > 3.hours.from_now - 10.minutes` or something similar. experiment with plus and minus and ago/from_now. I have problems thinking about time.

ormuriauga 2010-09-10 08:43:21

actually, check your config (in rails3 config/application.rb), there you can set the timezone of your app which will automatically compensate for you.

ormuriauga 2010-09-10 08:47:06

Answer 3

+2 A:

It sounds like your database column is of type time rather than datetime or timestamp. This will only store the time and when it is converted to a Time instance in ruby (which does support day, month, year, etc) the default values are used for day, month, year which is why you're seeing the year 2000.

You probably need to update your database column to be datetime or timestamp if that is the problem as it sounds like you'll want the day, month, year parts of the time anyway. In which case you're comparisons will work.

Shadwell 2010-09-10 08:21:21

yeah, this sounds plausible.

ormuriauga 2010-09-10 08:23:13

yes, the column is of the type time. I've been trying the created_at part and it still doesn't work..

Brian 2010-09-10 08:25:18

Not sure what you mean. I didn't mention created_at.

Shadwell 2010-09-10 08:35:34

yup, I changed it to datetime and it seems to work with u.online.last_seen > 10.minutes.ago

Brian 2010-09-10 08:52:07

thank you to both of you for the help

Brian 2010-09-10 08:52:23

ansaurus

tags:

views:

answers:

Ruby on Rails Time.now

related questions