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
We continue to extend the interface with more and more functions to retrieve and save data based on different keys.
Should we consider only having a single method in the interface, generic retrieve and send data methods based on an arbitrary key?
Then, we can create a wrapper for the interface that can utilize the generic retrieve and send data methods for all the different keys.
This may simplify the design of the interface and make it easier to implement the method for other databases. However, we do not know realistically how often users will implement the interface for other databases and whether or not this generic function makes sense for those other databases.
The text was updated successfully, but these errors were encountered:
We continue to extend the interface with more and more functions to retrieve and save data based on different keys.
Should we consider only having a single method in the interface, generic retrieve and send data methods based on an arbitrary key?
Then, we can create a wrapper for the interface that can utilize the generic retrieve and send data methods for all the different keys.
This may simplify the design of the interface and make it easier to implement the method for other databases. However, we do not know realistically how often users will implement the interface for other databases and whether or not this generic function makes sense for those other databases.
The text was updated successfully, but these errors were encountered: