ENH Database support for tuples and list #26
Merged
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.
Description
This PR adds database support for parameters which are tuples/lists. We assume, for the time being at least, that most parameters are not long tuples/lists. Therefore, they are handled by splitting the values and appending an index to the column keys in the database. A potential use case could be to have a single parameter which is a tuple representing a minimum and a maximum.
E.g.
a["b"]
in the nested dictionaries below:will have column keys of
a.b[0]
anda.b[1]
.Checklist
PR Type:
Address issues:
Testing
In use with
cxic0415
andcxic0515
processing.Screenshots