Skip to content

fix(cypher): temporal historical canonicalization/comparison tranche#1409

Merged
lmeyerov merged 2 commits into
masterfrom
issue-1406-temporal-comparison-tranche
May 9, 2026
Merged

fix(cypher): temporal historical canonicalization/comparison tranche#1409
lmeyerov merged 2 commits into
masterfrom
issue-1406-temporal-comparison-tranche

Conversation

@lmeyerov
Copy link
Copy Markdown
Contributor

@lmeyerov lmeyerov commented May 9, 2026

Summary

  • close the remaining temporal canonicalization mismatch in direct-Cypher for historical named-zone datetime parsing
  • align comparison parity between named-zone-derived and explicit-offset datetime literals
  • add focused regressions for historical Stockholm named-zone canonicalization and equality

Issue

Testing

  • python -m pytest -q graphistry/tests/compute/gfql/cypher/test_temporal_text.py::test_normalize_temporal_constructor_text_uses_neo4j_historical_stockholm_offset graphistry/tests/compute/gfql/cypher/test_lowering.py::test_string_cypher_parses_datetime_historical_named_zone_literals graphistry/tests/compute/gfql/cypher/test_lowering.py::test_string_cypher_compares_historical_named_zone_and_explicit_offset_datetime
  • uv run ruff check graphistry/compute/gfql/temporal_text.py graphistry/tests/compute/gfql/cypher/test_temporal_text.py graphistry/tests/compute/gfql/cypher/test_lowering.py
  • python -m pytest -q graphistry/tests/compute/gfql/cypher/test_temporal_text.py graphistry/tests/compute/gfql/cypher/test_lowering.py -k "historical_named_zone or parses_datetime_named_zone_literals or supports_datetime_comparison_consistent_with_sort_order or executes_temporal_datetime_constructor_recomputes_named_zone_offset_for_new_date"

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.

[META-split] Direct-Cypher wrong-rows tranche B: temporal comparison/canonicalization

1 participant