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

Improve doc about 0000-00-00 date/datetime when loc is not UTC #821

Open
dolmen opened this issue Jun 15, 2018 · 1 comment
Open

Improve doc about 0000-00-00 date/datetime when loc is not UTC #821

dolmen opened this issue Jun 15, 2018 · 1 comment

Comments

@dolmen
Copy link
Contributor

dolmen commented Jun 15, 2018

In #783 some documentation has been added about the driver behaviour for 0000-00-00 when parseTime is true.

But the zero value of time.Time is in location UTC. What happens when the loc option is set to another timezone than UTC?
The documentation should clarify this.

Cc: @methane

@dolmen dolmen changed the title Improve doc about 0000-00-00 date/datetime Improve doc about 0000-00-00 date/datetime when loc is not UTC Jun 15, 2018
@methane
Copy link
Member

methane commented Jun 15, 2018

Zero value is well defined world. It's very clear.
And it's not UTC, it's loc is nil.

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

No branches or pull requests

2 participants