#6581 Date column bug - Ruby on Rails

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

This project is archived and is in readonly mode.

#6581 ✓invalid

Date column bug

Reported by Jan Bernacki | March 15th, 2011 @ 09:23 AM

Hello.

create_table :downloads do |t|
  t.date :downloaded_at
  t.integer :count, :default => 0
end

Download.create(:downloaded_at => Time.now)
d = Download.first # => #<Download id: 1, downloaded_at: "2011-03-15", count: 0>
Download.where(:downloaded_at => d.downloaded_at) # => []

Database Mysql, SQLite, rails 3.0.5

if I use Download.create(:downloaded_at => Date.current), I find it after.

Maybe it's not a Bug, but intuitively, it seems that Time.now is correct.

Comments and changes to this ticket

Josh Kalderimis March 15th, 2011 @ 12:53 PM
- State changed from “new” to “invalid”
- Importance changed from “” to “Low”
Hi Releu,

The difference between Time.now and Date.current is that Time.now has a higher precision.

When you create a Download using Time.now it is cast to a Date, thus losing its precision. But when you query for a Download using Time.now that precision is not cast but instead just passed to your DB. You can check this for yourself by looking at the logs.

I will close this issue as it is not a bug.

Thanks

Josh
You flagged this item as spam.
Jan Bernacki March 15th, 2011 @ 01:07 PM
Hello Josh,

Thanks for the explanation.

Yan