-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Graph Database #16
Labels
Milestone
Comments
using neomodel version 3.2.9 because of this issue neo4j-contrib/neomodel@e3e4e4e#commitcomment-31025237 |
code-inflation
added a commit
that referenced
this issue
Nov 12, 2018
code-inflation
added a commit
that referenced
this issue
Nov 12, 2018
code-inflation
added a commit
that referenced
this issue
Nov 12, 2018
code-inflation
added a commit
that referenced
this issue
Nov 12, 2018
code-inflation
added a commit
that referenced
this issue
Nov 12, 2018
code-inflation
pushed a commit
that referenced
this issue
Nov 12, 2018
code-inflation
added a commit
that referenced
this issue
Nov 12, 2018
code-inflation
added a commit
that referenced
this issue
Nov 19, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Description of problem
Currently the data knowledge graph data is stored in a relational database. To improve performance and to better match our data structure, we need to change it to a graph database.
Solution
A clear and concise description of what you want to happen.
Additional context
Add any other context or screenshots about the feature request here.
Criteria for acceptance
The text was updated successfully, but these errors were encountered: