Skip to content

[engine] Cypher MERGE value matching disagrees with MATCH (FLOAT widening and temporal vs STRING property) #9693

Closed

Description

@github-actions

Automated consolidation of related issues in engine, carrying the highest severity of the issues it replaces (severity:major).

Each issue above was closed as a duplicate of this one. If a grouping is wrong, reopen that issue and strike it from this list.

Opened by the merge-related-issues workflow (run).

Activity

  1. added
    parent-issueLabel to mark issues used to group related topics
    engineCore engine: document/schema API
    severity:majorA feature is broken or returns wrong results, with no practical workaround
    on Oct 10, 2026
  2. added this to the 26.11.1 milestone on Oct 10, 2026
  3. self-assigned this
    on Oct 10, 2026
  4. added a commit that references this issue on Oct 10, 2026
  5. robfrank commented on Oct 10, 2026

    @robfrank
    Collaborator

    Fixed by #9696. Cypher MERGE used its own value comparison, which did not agree with MATCH. It now uses the same check MATCH uses, so the two clauses find the same records. This applies to node and relationship patterns, indexed and unindexed lookups, parameters, and the merge.relationship procedure.

    Still open: #9695 tracks whether a value the declared type converts on write (a temporal or a number written into a STRING property) should be matched again by the same pattern, in both MATCH and MERGE.


    ❤️ Thanks for helping make ArcadeDB better! ArcadeDB is free and open source, sustained by its community. If it's useful to you or your company, please consider becoming a sponsor to keep development going.

  6. removed
    in progressThe team is actively working on this issue
    on Oct 10, 2026
  7. added a commit that references this issue on Oct 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugengineCore engine: document/schema APIopencypherparent-issueLabel to mark issues used to group related topicsseverity:majorA feature is broken or returns wrong results, with no practical workaround

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions