This project is archived and is in readonly mode.
TimeWithZone#xmlschema formatting loses leading zeros on microseconds
Reported by Levent | June 2nd, 2010 @ 03:59 PM
# In ActiveSupport's TimeWithZone#xmlschema
>> Time.zone.parse("2010-06-02T14:23:24.000709Z").iso8601(6)
# "2010-06-02T14:23:24.709Z"
# In Ruby's Time#xmlschema
>> Time.parse("2010-06-02T14:23:24.000709Z").iso8601(6)
=> "2010-06-02T14:23:24.000709Z"
I'm just looking into tests to prove this
Comments and changes to this ticket
-
Levent June 3rd, 2010 @ 03:38 PM
It seems the problem is with ruby's usec method which loses the zeros.
Ruby doesn't use the usec method within xmlschema -
Levent June 3rd, 2010 @ 03:45 PM
My bad that is the expected behaviour of usec so the issue is with activesupport's method
-
Santiago Pastorino February 2nd, 2011 @ 04:38 PM
- State changed from new to open
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.
Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
-
Santiago Pastorino February 2nd, 2011 @ 04:38 PM
- State changed from open to stale
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>