Fix schema permission (#18)

## [1.3.2] - 2024-11-13
#### [@rickypid](https://github.com/rickypid)

Improve documentations

### Fixed

* Fixed schema `chats` permission after view creation

Author: rickypid

CHANGELOG.md

@@ -1,3 +1,12 @@
+## [1.3.2] - 2024-11-13
+#### [@rickypid](https://github.com/rickypid)
+
+Improve documentations
+
+### Fixed
+
+* Fixed schema `chats` permission after view creation
+
 ## [1.3.1] - 2024-11-12
 #### [@rickypid](https://github.com/rickypid)
 

doc/docs/guides/supabse-indexes.md

@@ -3,6 +3,8 @@ id: supabase-indexes
 title: Database Indexes
 ---
 
+## `chats.messages` indexes
+
 These indexes are added to improve the performance of foreign keys in database tables:
 
 ```sql

doc/docs/guides/supabse-trigges.md

@@ -3,7 +3,9 @@ id: supabase-triggers
 title: Database Triggers
 ---
 
-This is an example of a triggers that sets room's `lastMessages` to the most recent message sent once recieved in Supabase.
+## Update room last message
+
+This is a trigger that sets room's `lastMessages` to the most recent message sent once recieved in Supabase.
 
 ```sql
 CREATE OR REPLACE FUNCTION chats.update_last_messages()
@@ -29,6 +31,8 @@ CREATE TRIGGER update_last_messages_trigger
 EXECUTE FUNCTION chats.update_last_messages();
 ```
 
+## Set message status to sent
+
 "This trigger, on the other hand, is responsible for setting the message status to `sent` when it is added to the `messages` table:
 
 ```sql
@@ -48,6 +52,8 @@ CREATE TRIGGER update_status_before_insert
     FOR EACH ROW EXECUTE FUNCTION chats.set_message_status_to_sent();
 ```
 
+## Handle new user from `auth.users`
+
 "This trigger, is responsible for replicate `auth.users` table rows in `chats.users` table, this is to avoid exposing user data :
 
 ```sql

doc/docs/guides/supabse-views.md

@@ -0,0 +1,34 @@
+---
+id: supabase-views
+title: Database Views
+---
+
+## Rooms view
+
+This is a view of `rooms` table, this view allows you to obtain the name of the sender of the message dynamically in direct rooms, based on the logged-in user the name of the correspondent is displayed.
+
+```sql
+DROP VIEW IF EXISTS chats.rooms_l;
+create view chats.rooms_l
+    WITH (security_invoker='on') as
+select
+    r.id,
+    r."imageUrl",
+    r.metadata,
+    case
+        when r.type = 'direct' and auth.uid() is not null then
+            (select coalesce(u."firstName", '') || ' ' || coalesce(u."lastName", '')
+             from chats.users u
+             where u.id = any(r."userIds") and u.id <> auth.uid()
+             limit 1)
+        else
+            r.name
+        end as name,
+    r.type,
+    r."userIds",
+    r."lastMessages",
+    r."userRoles",
+    r."createdAt",
+    r."updatedAt"
+from chats.rooms r;
+```

doc/package.json

@@ -1,6 +1,6 @@
 {
   "name": "flutter-supabase-chat-core",
-  "version": "1.3.1",
+  "version": "1.3.2",
   "private": true,
   "scripts": {
     "docusaurus": "docusaurus",

doc/sidebars.ts

@@ -33,6 +33,7 @@ const sidebars: SidebarsConfig = {
           'guides/supabase-usage',
           'guides/supabase-security',
           'guides/supabase-triggers',
+          'guides/supabase-views',
           'guides/supabase-indexes',
       ],
     },

example/pubspec.yaml

@@ -2,7 +2,7 @@ name: example
 description: A new Flutter project.
 publish_to: 'none'
 
-version: 1.3.1
+version: 1.3.2
 
 environment:
   sdk: '>=3.4.0 <4.0.0'

example/utils/prepare.ps1

@@ -20,3 +20,4 @@ Invoke-Expression "$psqlCommand -f .\sql\02_database_trigger.sql"
 Invoke-Expression "$psqlCommand -f .\sql\03_database_policy.sql"
 Invoke-Expression "$psqlCommand -f .\sql\04_storage.sql"
 Invoke-Expression "$psqlCommand -f .\sql\05_database_view.sql"
+Invoke-Expression "$psqlCommand -f .\sql\99_database_schema_permission.sql"

example/utils/prepare.sh

@@ -14,4 +14,5 @@ psql -U $user -h $hostname -p $port -d $database -f ./sql/01_database_schema.sql
 psql -U $user -h $hostname -p $port -d $database -f ./sql/02_database_trigger.sql
 psql -U $user -h $hostname -p $port -d $database -f ./sql/03_database_policy.sql
 psql -U $user -h $hostname -p $port -d $database -f ./sql/04_storage.sql
-psql -U $user -h $hostname -p $port -d $database -f ./sql/05_database_view.sql
+psql -U $user -h $hostname -p $port -d $database -f ./sql/05_database_view.sql
+psql -U $user -h $hostname -p $port -d $database -f ./sql/99_database_schema_permission.sql

example/utils/sql/99_database_schema_permission.sql

@@ -0,0 +1,7 @@
+GRANT USAGE ON SCHEMA chats TO anon, authenticated, service_role;
+GRANT ALL ON ALL TABLES IN SCHEMA chats TO anon, authenticated, service_role;
+GRANT ALL ON ALL ROUTINES IN SCHEMA chats TO anon, authenticated, service_role;
+GRANT ALL ON ALL SEQUENCES IN SCHEMA chats TO anon, authenticated, service_role;
+ALTER DEFAULT PRIVILEGES FOR ROLE postgres IN SCHEMA chats GRANT ALL ON TABLES TO anon, authenticated, service_role;
+ALTER DEFAULT PRIVILEGES FOR ROLE postgres IN SCHEMA chats GRANT ALL ON ROUTINES TO anon, authenticated, service_role;
+ALTER DEFAULT PRIVILEGES FOR ROLE postgres IN SCHEMA chats GRANT ALL ON SEQUENCES TO anon, authenticated, service_role;