cartodb-postgresql

Author	SHA1	Message	Date
Sandro Santilli	f8180123eb	Grant permission to run table-info functions to public This is needed as a way to migrate from versions < 0.2.0 See #36	10 years ago
Sandro Santilli	01ae7b8c10	Drop role management Roles are not created anymore, previously private functions for table information extraction (CDB_UserTables, CDB_TableIndexes, CDB_ColumnNames, CDB_ColumnType) will now be callable by anyone while only returning information about tables over which the calling user has SELECT privilege. Closes #36	10 years ago
Sandro Santilli	0082138503	Do not force DROP FUNCTION but rely on CREATE OR REPLACE We'll bet on no old signature being left around. Presence of an old signature would break at runtime with a message like: ERROR: function CDB_UserTables() is not unique Closes #25	10 years ago
Sandro Santilli	055efe04aa	Do not assume existance of a "publicuser" role in CDB_UserTables Closes #5 (take 2)	11 years ago
Sandro Santilli	9b6f9e21f2	Stick with user tables being in public ... but workaround extension code replacing "public." with "cartodb."	11 years ago
Sandro Santilli	15740f2ef6	Enable running all tests via "installcheck" NOTE: also makes CDB_TableMetadata triggers still functional when user quota and varnish invalidation functions are missing from the database (currently installed by cartodb ruby)	11 years ago
Sandro Santilli	2f1fdf5a15	Copy cartodb lib/sql scripts from CDB_CartodbfyTable branch	11 years ago