Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

time: RFC3339 without time zone #5016

Closed
gopherbot opened this issue Mar 9, 2013 · 4 comments

Comments

Projects
None yet
2 participants
@gopherbot
Copy link

commented Mar 9, 2013

by raul.san@sent.com:

The time stamps related to RFC3339 use a time zone but it would be useful to have them
also without time zone, so could be used in databases like SQLite3 and MySQL which have
SQL type for timestap without time zone.

The best solution would be:

    RFC3339Z     = "2006-01-02T15:04:05Z07:00"
    RFC3339NanoZ = "2006-01-02T15:04:05.999999999Z07:00"

    RFC3339     = "2006-01-02T15:04:05Z"
    RFC3339Nano = "2006-01-02T15:04:05.999999999Z"

And it is not a great problem for actual software.
@gopherbot

This comment has been minimized.

Copy link
Author

commented Mar 9, 2013

Comment 1 by raul.san@sent.com:

Or the new ones could be names ading UTC at the name, so there would not have to be
changed the actual RFC3339 and RFC3339Nano formats:
    RFC3339UTC     = "2006-01-02T15:04:05Z"
    RFC3339NanoUTC = "2006-01-02T15:04:05.999999999Z"
@gopherbot

This comment has been minimized.

Copy link
Author

commented Mar 9, 2013

Comment 2 by raul.san@sent.com:

Or the new ones could be named adding UTC at the name, so there would not have to be
changed the actual RFC3339 and RFC3339Nano formats:
    RFC3339UTC     = "2006-01-02T15:04:05Z"
    RFC3339NanoUTC = "2006-01-02T15:04:05.999999999Z"
@gopherbot

This comment has been minimized.

Copy link
Author

commented Mar 9, 2013

Comment 3 by raul.san@sent.com:

Please remove this issue. It works when is passed a time in UTC only.
@minux

This comment has been minimized.

Copy link
Member

commented Mar 9, 2013

Comment 4:

Status changed to Retracted.

@golang golang locked and limited conversation to collaborators Jun 24, 2016

This issue was closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.