Skip to content
This repository has been archived by the owner on Apr 17, 2018. It is now read-only.

Time property is not stored properly with respect to utc_offset values #231

Open
dantler opened this issue Oct 10, 2012 · 1 comment
Open

Comments

@dantler
Copy link

dantler commented Oct 10, 2012

Hi,

It seems like DataMapper and Ruby have two different ideas about how to store and retrieve Time objects. The following few lines show the issue. Pay particular attention to the offsets!

t
# => #<Time @value=2012-10-11 13:05:40 +0900>
Meeting.create(:begin => t)

m = Meeting.all(:begin => t)
m.query
# => #<DataMapper::Query ... @conditions=(begin = 2012-10-11 13:05:40 +0900)>
m.first
# => #<Meeting @id=2 @begin=2012-10-11 13:05:40 -0700 ...>

I have created a repository with the issue using Postmodern's bug report template, see: https://github.com/dantler/dm-bug-report . Please let me know if I can provide more assistance!

Thanks,
David

@dantler
Copy link
Author

dantler commented Oct 12, 2012

I updated this issue with a simpler problem description. Figure it deserves a bump.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant