numerus/verify/set_cookie.sql

-- Verify numerus:set_cookie on pg

begin;

select has_function_privilege('public.set_cookie(text)', 'execute');

rollback;
Add a function to set request settings and the role I did not like the idea that it was the Go server who should set values such as request.user or set the role, because this is mostly something that only the database wants for itself, such as when calling logout. I am also planning to use these setings for row security with the user’s id, that the Go application has no need for, but with the current approach i would need to return it from check_cookie so that it can return it back to the database when acquiring the connection. I would have used the same function to set the settings and the role, but security definer functions—obviously in retrospect—can not set the role, because then could switch to any role of the user that defined the function, not the roles they are member of. Thus, a new function. I did not want to do that every time i needed the database connection within the same request, because it would perform the same operations each time—it is the same cookie, afterall—, so new connections are request scoped and passed along in the context. 2023-01-19 12:07:32 +00:00			`-- Verify numerus:set_cookie on pg`

			`begin;`

			`select has_function_privilege('public.set_cookie(text)', 'execute');`

			`rollback;`