This is consistent with cartodb behaviour, but not exactly the same as the contract that the 'public' role guarantees access to public resources. Possibly a better fix would be to audit (ug) everything and make sure that it's really using the public role to mean public, rather than the 'publicuser' connection role. That CDB creates.
14 lines
475 B
SQL
14 lines
475 B
SQL
CREATE ROLE publicuser;
|
|
CREATE TABLE pub(a int);
|
|
CREATE TABLE prv(a int);
|
|
GRANT SELECT ON TABLE pub TO publicuser;
|
|
REVOKE SELECT ON TABLE prv FROM publicuser;
|
|
SELECT CDB_UserTables() ORDER BY 1;
|
|
SELECT 'all',CDB_UserTables('all') ORDER BY 2;
|
|
SELECT 'public',CDB_UserTables('public') ORDER BY 2;
|
|
SELECT 'private',CDB_UserTables('private') ORDER BY 2;
|
|
SELECT '--unsupported--',CDB_UserTables('--unsupported--') ORDER BY 2;
|
|
DROP TABLE pub;
|
|
DROP TABLE prv;
|
|
DROP ROLE publicuser;
|