Go to file
jordi fita mas b63f7e7c54 Change find_user_role’s and login’s volatility to stable
According to PostgreSQL’s manual[0]:

  “STABLE indicates that the function cannot modify the database, and
   that within a single table scan it will consistently return the same
   result for the same argument values, but that its result could change
   across SQL statements.”

This definition matches both functions.  Moreover, find_user_role did
not need to be written in plpgsql, that i assume—but did not test—are
slower than sql functions.

[0]: https://www.postgresql.org/docs/14/sql-createfunction.html
2023-01-16 10:02:31 +01:00
cmd/numerus Downgrade pgx to v4 2023-01-15 20:45:45 +01:00
debian Add files to build Debian package 2023-01-15 22:56:49 +01:00
deploy Change find_user_role’s and login’s volatility to stable 2023-01-16 10:02:31 +01:00
pkg Downgrade pgx to v4 2023-01-15 20:45:45 +01:00
revert Setup authentication schema and user relation 2023-01-13 20:30:21 +01:00
test Change find_user_role’s and login’s volatility to stable 2023-01-16 10:02:31 +01:00
verify Setup authentication schema and user relation 2023-01-13 20:30:21 +01:00
web/template Add the simplest possible web server to test login 2023-01-13 20:53:43 +01:00
COPYING Rename LICENSE to COPYING 2023-01-15 04:08:35 +01:00
go.mod Downgrade pgx to v4 2023-01-15 20:45:45 +01:00
go.sum Downgrade pgx to v4 2023-01-15 20:45:45 +01:00
sqitch.conf Setup authentication schema and user relation 2023-01-13 20:30:21 +01:00
sqitch.plan Setup authentication schema and user relation 2023-01-13 20:30:21 +01:00