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
For example, in issue #20 , User is explicitly being passed to find() means that the user expects the historian to know this type, in which case we can take the liberty of registering it automatically (if it is not already registered). To avoid the possibility of clobbering an existing type the call should throw an exception if the TYPE_ID already exists.
There may be other historian methods where this kind of automatic registration could be useful.
The text was updated successfully, but these errors were encountered:
Ok, this functionality has been added to find() and is available from #v0.15.18 .
historian.register_type() will clobber whatever was registered before (which was the previous behaviour anyway), and historian.type_registry.register_type() will, by default, raise in such a scenario but this can be overridden with a replace=True flag.
For example, in issue #20 ,
User
is explicitly being passed tofind()
means that the user expects the historian to know this type, in which case we can take the liberty of registering it automatically (if it is not already registered). To avoid the possibility of clobbering an existing type the call should throw an exception if theTYPE_ID
already exists.There may be other historian methods where this kind of automatic registration could be useful.
The text was updated successfully, but these errors were encountered: