You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, using_spinedb attempts to clear whatever convenience functions have been created so far. So if the user modifies their DB, further calls to using_spinedb should reflect the new contents of the DB. Some users have reported that some artifacts from older calls remain, but I haven't been able to reproduce that.
We could be more aggressive in clearing the older convenience functions by assigning nothing to them.
But also, this should be optional. In case the user wants to use multiple DBs together, that should also be possible.
The text was updated successfully, but these errors were encountered:
At the moment, using_spinedb attempts to clear whatever convenience functions have been created so far. So if the user modifies their DB, further calls to using_spinedb should reflect the new contents of the DB. Some users have reported that some artifacts from older calls remain, but I haven't been able to reproduce that.
We could be more aggressive in clearing the older convenience functions by assigning nothing to them.
But also, this should be optional. In case the user wants to use multiple DBs together, that should also be possible.
The text was updated successfully, but these errors were encountered: