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

interpret number literals compared against time as nanoseconds from epoch #3721

Merged
merged 2 commits into from
Aug 18, 2015

Conversation

DanielMorsing
Copy link
Contributor

fixes #3719

@DanielMorsing
Copy link
Contributor Author

@beckettsean @otoolep

@otoolep
Copy link
Contributor

otoolep commented Aug 18, 2015

Works for me. This warrants a CHANGELOG update IMHO.

@otoolep
Copy link
Contributor

otoolep commented Aug 18, 2015

https://github.com/influxdb/influxdb.com/issues/229 to update the docs.

@otoolep
Copy link
Contributor

otoolep commented Aug 18, 2015

+1 on the change.

DanielMorsing added a commit that referenced this pull request Aug 18, 2015
interpret number literals compared against time as nanoseconds from epoch
@DanielMorsing DanielMorsing merged commit e2db51e into master Aug 18, 2015
@DanielMorsing DanielMorsing deleted the timeliteral branch August 20, 2015 18:45
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

Successfully merging this pull request may close these issues.

[0.9.3 nightly] comparison operators on epoch timestamps always return true if no units supplied
3 participants