Skip to content
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

Conversion to Graph Database #407

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from
Draft

Conversation

DMalone87
Copy link
Collaborator

@DMalone87 DMalone87 commented Aug 14, 2024

  • Done: Convert to graph database
  • Done: Update requirements
  • Done: Remove SQLAlchemy
  • In Progress: Update API to support db changes
  • Validation: Complete the data model conversion
  • TODO: Update tests to use the new DB

- Convert to graph-based data model
- Update requirements
- Todo: Update API to support db changes
- Todo: Complete the data model conversion
- Todo: remove SQLAlchemy
@DMalone87 DMalone87 added enhancement New feature or request backend labels Aug 21, 2024
@DMalone87 DMalone87 self-assigned this Aug 21, 2024
Convert routes to use neomodel instead of SQLAlchemy
- Update docker-compose.yml to use the new neo4j container
- Make additional corrections to the db models
Additionally: Change env variable w/PDT to NPDI
Our env vars will be changing anyway, so we might
as well make this change now.
@DMalone87
Copy link
Collaborator Author

Most recent update finally has the Graph DB image replacing the PGSQL one. I'm using version 5.23-community

@DMalone87 DMalone87 changed the title Conversion to graph-based data model: Stage 1 Conversion to Graph Database Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant