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
As in the title - I don't see any function in the 'public API' of migratum:* responsible for that.
Is it assumed that users disassemble the provider and driver objects and then drop connection on their own? If not then can users be sure there will be no memory leaks when simply setting drivers connection to nil or discarding the object provided by `(migratum.provider.local-path:make-local-path-provider ...)?
There is no information about teardown in the docs/README.
The text was updated successfully, but these errors were encountered:
As in the title - I don't see any function in the 'public API' of
migratum:*
responsible for that.Is it assumed that users disassemble the provider and driver objects and then drop connection on their own? If not then can users be sure there will be no memory leaks when simply setting drivers connection to nil or discarding the object provided by `(migratum.provider.local-path:make-local-path-provider ...)?
There is no information about teardown in the docs/README.
The text was updated successfully, but these errors were encountered: