Neo4j DateTime Zone ID Persistence and Local Conversion Limits

Neo4j implements the ISO 8601 standard for temporal data, allowing DateTime objects to store specific timezone identifiers or offsets. This capability is essential for maintaining regional context across distributed datasets.

A design challenge arises when converting these zoned representations into LocalDateTime for regional reporting. Because LocalDateTime is timezone-unaware by design, the conversion process effectively strips the zone ID, potentially creating ambiguity when the same wall-clock time exists across multiple regional offsets.

Given these constraints, what is the expected behavior when comparing a DateTime with a specific zone ID against a LocalDateTime value? Does the engine perform an implicit conversion to the system's local time, or does it treat the comparison as a literal value match regardless of the original zone?