Features/adjust db interface #626
Merged
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
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.
Solves #311
With this branch, the ego.io is not needed anymore. The functions to create a database connection and store connection settings are now part of eTraGo (tools.db). I basically copied function from ego.io, I hope that was fine.
The usage of the db section in the args did not changed, but the connection settings are now stored in a different file (.etrago_database/config.ini).
@gnn: Is the general procedure fine?
@KathiEsterl or @CarlosEpia: Could you test the installation and start a small test calculation to make sure that it is working correctly? I already tested it, but it would be better to try it out in another setting as well.