Improving access control: granting specific permissions to functions in databases

One of the reasons functions are created is to execute other queries before returning the results of a regular table query. The issue is that functions necessarily inherit the permissions of the table they return. In this case, auditing access to queries is impossible because a user could make a query to the function or directly to the table from which they want to obtain data, since they share permissions. Specific permissions should be able to be specified for functions, as is already done with tables and views.

The issue names database functions, tables, and views but no repository files or tests. Start by locating the permission and metadata handling entry points, then compare how table and view access is represented. Done means functions can receive distinct permissions from the tables they query, with coverage for direct table access and function-based access.

Written by the indexing model from the issue text.