Skip to content

Updating of Neo4j DB version results in Python interface issues in API #10

@james-skelton

Description

@james-skelton

The API currently uses the Neo4j Docker 3.5.34 container. When this was updated to 4.3.6, the API routes to interface with Neo4j failed. I will investigate this further with a local example and update findings here.

The reason that py2neo was selected over the neo4j driver for the API was because the neo4j driver did not have a way to return the data for edges as JSON. When edges were returned, the available data was superficial and did not have edge attributes.

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