postgrahpql generates some really useful CRUD operations on each table in the schema that is set in the connection string the postgraphql server.
However, specifically for users (registration, update, delete, login) we'll want custom functions. The only way to do this is to 'hide' the user tables out of the schema that the connection string specifies.
Likely we'll have
flingapp[.userfunction] (anon, user, admin access)
does stuff in
flingapp_hidden (user, admin access)
does stuff in
flingapp_private (admin access)
postgrahpql generates some really useful CRUD operations on each table in the schema that is set in the connection string the postgraphql server.
However, specifically for users (registration, update, delete, login) we'll want custom functions. The only way to do this is to 'hide' the user tables out of the schema that the connection string specifies.
Likely we'll have
flingapp[.userfunction]
(anon, user, admin access) does stuff inflingapp_hidden
(user, admin access) does stuff inflingapp_private
(admin access)