Michael Crismali
Michael Crismali
+1 this is important
@peck, are you still hacking on this?
This c1c16fb7713464ccce79818cd7d0d6a856fae26b is a start on this.
Is there a step missing in your description above? I played with this a bit locally in a Rails 4.1 console: ``` ruby x = Time.now #=> 2015-03-24 11:56:28 -0500...
This issue is difficult to solve without another major version release. We could store datetimes as the number of milliseconds and hack in a solution to make it work with...
That could work well. That way when we hit the next major release we could swap drop datetime and just rename timestamp to datetime.
Thanks for using the gem and opening up this issue. We'll play around with this a bit more but I'm leaning towards the new data type option. Seems like the...
Right now there isn't an immediate plan, but PRs are more than welcome 👍
This could be convenient. For the type coercion, things should be in line with how Rails does it out of the box. Anyway, pull requests are encouraged =)
I haven't run into the problem myself, but I believe there are a few approaches you could take. If you're using [Teaspoon](https://github.com/jejacks0n/teaspoon) as your test runner [there are options for...