As this provider is based on JavaScript SProcs, it would be nice to have them deployed and (optionally) updated whenever a new version is published.
One way to do it, is to have a separated entity within the same collection of EntityType == Sproc where we would keep a reference to the current sprocs installed, and which version to use. That table would be read at startup and (optionally) if the version deployed doesn't match the one with the nuget package, it should update them.
This feature is optional as it would require the credentials to have access at the collection to create sprocs and sometimes it isn't desirable.
galvesribeiro
commented
6 years ago
As this provider is based on JavaScript SProcs, it would be nice to have them deployed and (optionally) updated whenever a new version is published.
One way to do it, is to have a separated entity within the same collection of
EntityType == Sprocwhere we would keep a reference to the current sprocs installed, and which version to use. That table would be read at startup and (optionally) if the version deployed doesn't match the one with the nuget package, it should update them.This feature is optional as it would require the credentials to have access at the collection to create sprocs and sometimes it isn't desirable.