Merged
Conversation
This is so we can reformat suitably for neo4j.
This is so we can assign labels to nodes based on the dataset.
This is so we can uniquely identify nodes and relationships when exporting to neo4j.
This is so we can combine all the code we've written thus far into a module that can be run from the command line. Update README.md with new instructions for extracting table dependencies.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This branch creates functions that reformats and exports the dictionaries outputted by the
Extractorclass so it can then be exported into neo4j. It then brings the code together so you can extract and export table dependencies from a set of SQL scripts into theneo4j/subdirectory.Changes
The high-level changes made in this PR are:
Please see the commit history for more detailed changes.
Check