feat: analyze a whole database and find its relationships [WIP] [Skunkworks] - #207
Draft
lerouxb wants to merge 1 commit into
Draft
feat: analyze a whole database and find its relationships [WIP] [Skunkworks]#207lerouxb wants to merge 1 commit into
lerouxb wants to merge 1 commit into
Conversation
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
2 participants
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.
I should probably change the interface to take all the schemas at once which should make it possible to check references to things other than _id. ie. make _id and every other objectid/uuid field that was selected as a candidate for any collection a possible target field. Although then you have the problem where if two collections reference a third one's _id, then those two would also be referencing each other. Which is not what you want 🤔