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

CIP2015-08-06 Date and Time #15

Merged
merged 13 commits into from Jan 11, 2019
Merged

CIP2015-08-06 Date and Time #15

merged 13 commits into from Jan 11, 2019

Conversation

@thobe
Copy link
Contributor

@thobe thobe commented Dec 10, 2015

@thobe thobe force-pushed the thobe:date-time branch from 7382d94 to caa4f22 Dec 11, 2015
@petraselmer petraselmer added the CIP label Jun 20, 2016
@boggle boggle added the settled label Mar 27, 2017
@thobe thobe force-pushed the thobe:date-time branch 2 times, most recently from 246c567 to 5bb1489 Jan 19, 2018
@thobe thobe force-pushed the thobe:date-time branch from 5bb1489 to 10898ca Jan 30, 2018
@thobe thobe force-pushed the thobe:date-time branch from 1aa3fc5 to 4ae4ba8 Apr 10, 2018
@opencypher opencypher deleted a comment from sherfert Apr 10, 2018
@opencypher opencypher deleted a comment from sherfert Apr 10, 2018
@opencypher opencypher deleted a comment from sherfert Apr 10, 2018
@opencypher opencypher deleted a comment from sherfert Apr 10, 2018
@opencypher opencypher deleted a comment from sherfert Apr 10, 2018
@opencypher opencypher deleted a comment from sherfert Apr 10, 2018
@opencypher opencypher deleted a comment from boggle Apr 10, 2018
Instant values that occur at the same point in time, but that have a different timezone are not considered equal, and must therefore be ordered in some predictable way.
Cypher prescribes after the primary order of point in time, instant values be ordered by effective timezone offset, from west (negative offset from UTC) to east (positive offset from UTC).
This has the effect that times that represent the same point in time will be ordered with the time with the earliest local time first.
If two instant values represent the same point in time, and have the same timezone offset, but a different named timezone (this is possible for _DateTime_ only, since _Time_ only has an offset), these values are not considered equal, and ordered by the timezone identifier, alphabetically, as its third ordering component.

This comment has been minimized.

@sherfert

sherfert Apr 11, 2018
Contributor

If a has just an offset (no named timezone) and b has a named timezone (and everything else applies, i.e. same instant in time and same effective offset), then a < b.

@@ -785,6 +785,12 @@ Does lhs occur after rhs:
WITH date(...) AS lhs, date(...) AS rhs // or another temporal instant type
RETURN lhs > rhs

Instant values that occur at the same point in time, but that have a different timezone are not considered equal, and must therefore be ordered in some predictable way.
Cypher prescribes after the primary order of point in time, instant values be ordered by effective timezone offset, from west (negative offset from UTC) to east (positive offset from UTC).
This has the effect that times that represent the same point in time will be ordered with the time with the earliest local time first.

This comment has been minimized.

@sherfert

sherfert Apr 11, 2018
Contributor

This is not true for offsets greater than +12:00 or smaller than -12:00 (only true for Time, not for DateTime).

This comment has been minimized.

@thobe

thobe Apr 11, 2018
Author Contributor

True. It could be clarified that it has that effect for DateTime.

@boggle boggle merged commit 893ff93 into opencypher:master Jan 11, 2019
1 check passed
1 check passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants
You can’t perform that action at this time.