Closed dbrakenhoff closed 2 years ago
New proposed solution to this problem. Still a bit of a work in progress and I'm not sure whether this is the way to go yet.
Upsides:
pstore.oseries_models
propertyThere are some performance downsides to this implementation, but I'm not sure if they're really noticeable in practice...
Downsides:
A different proposed solution is presented in #68. This implementation creates a new library oseries_models
where the relationship between models and oseries will be stored.
Upsides:
pstore.oseries_models
propertyDownsides:
pstore.oseries_models
).Added in #62, closing issue.
The latest PR #49 adds functionality to keep track of models per oseries. This is useful to keep track of, e.g. for getting a list of models for a certain location. The downside of the current implementation is that it requires a run through all stored models to build this dictionary, which can take a few seconds when creating a Connector object linking to an existing database.
This issue is a reminder to maybe think about a faster more efficient way to keep track of this, i.e. store this relationship in a separate library that is updated with each
add_model()
anddel_model()
call. This avoids having to rebuild this dictionary each time you connect to the database. Or perhaps another solution...?