Skip to content

Usage of containment op instead of equal in property constraints (for lists and maps) #1461

@MuhammadTahaNaveed

Description

@MuhammadTahaNaveed

Usage of containment op instead of equal in property constraints (for lists and maps) outputs different results as compared to neo4j. Is this intentional?

Data:

CREATE (n {list:[1,2,3,4]}) return n

Query with issue:

MATCH (n {list:[4]}) return n

Results

Neo4j:

No rows returned

Age:

pg16=# SELECT * FROM cypher('issue_', $$MATCH (n {list:[4]}) return n$$) AS (u agtype);
                                         u                                          
------------------------------------------------------------------------------------
 {"id": 281474976710657, "label": "", "properties": {"list": [1, 2, 3, 4]}}::vertex
(1 row)

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions