You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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"
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"
by raul.san@sent.com:
The text was updated successfully, but these errors were encountered: