Refactor/flake db #789
Closed
Refactor/flake db #789
Conversation
This file contains 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
zonotope
force-pushed
the
refactor/flake-db
branch
from
9297938
to
42e6097
Compare
We've temporarily disabled simple subject crawl until we (re)introduce a generalized query optimization framework
This was referenced Jul 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This patch is part of a series that reorganizes the code in light of the new db types. This patch renames the
JsonLdDbrecord toFlakeDB, and puts the namespace that defines that record as well as all of it's supporting namespace under thefluree.db.flake....namespace hierarchy. I thinkJsonLdDbis ambiguous because all of our DB types represent json-ld data, but I thinkFlakeDBis more precise to how this specific DB type represents that data.