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
Passing the Connection Object should be a performance boost.
Create it as a Module Variable?
Add Handling for closing the Connection. This would mean adding functions to manage connections similar to how pssessions, jobs, or cimsessions work.
If the connection is not closed after each operation then the passed objects can be worked on directly this is a performance boost.
This could also mean that moving objects between databases would be much easier.
Returned Objects could contain a session ID as an origin session then this could be used a default operating connection. If this is done then a -KeePassConnection Parameter will need to be added to each object supporting function so it could be overrided and support pipeline and gathering the default session.
The text was updated successfully, but these errors were encountered:
This needs to be looked into for viability.
Current thoughts are:
Passing the Connection Object should be a performance boost.
Create it as a Module Variable?
Add Handling for closing the Connection. This would mean adding functions to manage connections similar to how pssessions, jobs, or cimsessions work.
If the connection is not closed after each operation then the passed objects can be worked on directly this is a performance boost.
This could also mean that moving objects between databases would be much easier.
Returned Objects could contain a session ID as an origin session then this could be used a default operating connection. If this is done then a -KeePassConnection Parameter will need to be added to each object supporting function so it could be overrided and support pipeline and gathering the default session.
The text was updated successfully, but these errors were encountered: