scoping the message_store
schema with security definer
#53
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was my attempt to fix the problem of scoping to the
message_store
and not to pollute the schema in every query. I am not PG expert so not sure if this path is the correct one. In general, the question is whether we need to scope it at all. But in case this sounds like a good solution to the problem #43 / #49 then feel free to accept it. I will also probably try to remove the schema prefix and rather limit it with the privileges for particular user.