cartodb-postgresql/test/CDB_UserTablesTest_expect

CREATE ROLE
CREATE TABLE
CREATE TABLE
GRANT
REVOKE
prv
pub
all|prv
all|pub
public|pub
private|prv
You are now connected to database "contrib_regression" as user "publicuser".
all_publicuser|pub
public_publicuser|pub
You are now connected to database "contrib_regression" as user "postgres".
DROP TABLE
DROP TABLE
DROP ROLE
Use 'publicuser' as public role, not 'public', closes #95. 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. 2015-07-07 20:49:28 +08:00			`CREATE ROLE`
Import cartodb/lib/sql/test, add search_path tweaker 2014-05-06 00:48:48 +08:00			`CREATE TABLE`
			`CREATE TABLE`
			`GRANT`
			`REVOKE`
			`prv`
			`pub`
			`all\|prv`
			`all\|pub`
			`public\|pub`
			`private\|prv`
updates tests 2015-07-27 16:37:07 +08:00			`You are now connected to database "contrib_regression" as user "publicuser".`
added tests for usertables to check private tables are not returned 2015-07-27 16:25:44 +08:00			`all_publicuser\|pub`
			`public_publicuser\|pub`
updates tests 2015-07-27 16:37:07 +08:00			`You are now connected to database "contrib_regression" as user "postgres".`
Import cartodb/lib/sql/test, add search_path tweaker 2014-05-06 00:48:48 +08:00			`DROP TABLE`
			`DROP TABLE`
Use 'publicuser' as public role, not 'public', closes #95. 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. 2015-07-07 20:49:28 +08:00			`DROP ROLE`