use nested datadir/network path for db supporting legacy #4698
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.
Created to solve #884.
It looks like some of this was implemented already, just a couple of missing
return
s for goerli and kiln-devnet.This is based on the assumption that this change would only be needed by Erigon itself, and that components like rpcdaemon ran separately would point to the correct datadir using a command line flag. Also an assumption that if a LOCK file exists at the root datadir that it would take precedence over the nested folder to be more backwards compatible?