Store dateTime statements as Neo4j datetime values#812
Draft
Store dateTime statements as Neo4j datetime values#812
Conversation
Statement values for the dateTime property type were written to Neo4j as plain ISO 8601 strings, leaving them un-queryable with Cypher's datetime functions (comparisons, ordering, range filtering). Builders registered with Neo4jValueBuilderRegistry can now return a Neo4jTypedValue, which SubjectUpdater wraps in a Cypher constructor (e.g. `datetime()`) on save. The mechanism extends cleanly to other typed Neo4j properties (date, point, duration, etc.) without further restructuring. > Result of back-and-forth with @malberts. Context: the NeoWiki codebase, > the existing PageDateTime / Neo4jQueryStore::extractTypedValues pattern, > and Neo4j Cypher temporal type docs. > <sub>Written by Claude Code, \`Opus 4.7 (1M context)\`</sub>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Statement values for the dateTime property type were written to Neo4j as
plain ISO 8601 strings, leaving them un-queryable with Cypher's datetime
functions (comparisons, ordering, range filtering). Builders registered
with Neo4jValueBuilderRegistry can now return a Neo4jTypedValue, which
SubjectUpdater wraps in a Cypher constructor (e.g.
datetime()) on save.The mechanism extends cleanly to other typed Neo4j properties (date,
point, duration, etc.) without further restructuring.