-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cosmos: Facility to auto-create stored procedure where client is sufficiently privileged #59
Comments
This was referenced Dec 8, 2018
Closed
bartelink
added a commit
that referenced
this issue
Dec 13, 2018
bartelink
added a commit
that referenced
this issue
Dec 13, 2018
In implementing this via #65, I ended up flipping the default to be on |
bartelink
added a commit
that referenced
this issue
Dec 13, 2018
bartelink
added a commit
that referenced
this issue
Dec 14, 2018
bartelink
added a commit
that referenced
this issue
Dec 19, 2018
bartelink
added a commit
that referenced
this issue
Dec 24, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Provisioning of the stored procedure is presently an explicitly separated act, driven by
Equinox.Cli init
, which fits in with DDL/DML separation concepts etc.However, in practice
a) keys are often provisioned with both DML (manipulate data) and DDL (create proc) permissions
b) as stored procedures are revised, new editions may need to be added
For the above, reasons, the connector should gain a
?provisionStoredProcNow
parameter that attempts to add if not present when requestedThe text was updated successfully, but these errors were encountered: