Community type 2 and 3 + update community type op

feature set

This feature enables the new community types as defined in the original doc:

• type 1: Topic: anyone can post or comment
• type 2: Journal: guests can comment but not post. only members can post.
• type 3: Council: only members can post or comment

test cases

for all tests, the account ismember will be a member of all the communities and notmember won't be.

• create a community type 1 hive-111119
• create a community type 2 hive-211119
• create a community type 3 hive-311119
• Community type 1 tests
• • post in community type 1 from member => not muted
• • post in community type 1 from non member => not muted
• • comment in community type 1 from member => not muted
• • comment in community type 1 from non member => not muted
• • comment in community type 1 from member at depth 2 => not muted
• Community type 2 tests
• • post in community type 2 from member => not muted
• • post in community type 2 from non member => muted
• • comment in community type 2 from member => not muted
• • comment in community type 2 from non member => not muted
• • comment in community type 2 from member at depth 2 => not muted
• Community type 3 tests
• • post in community type 3 from member => not muted
• • post in community type 3 from non member => muted
• • comment in community type 3 from member => not muted
• • comment in community type 3 from non member => muted
• • comment in community type 3 from member at depth 2 => not muted
• Change community type 1 to community type 3
• • change ismember to a mod (to validate that rules apply to roles above member and not just to member)
• • post in community type 3 from member => not muted
• • post in community type 3 from non member => muted
• • comment in community type 3 from member => not muted
• • comment in community type 3 from non member => muted

hive/db/sql_scripts/hive_post_operations.sql

@@ -39,9 +39,12 @@ declare
         __community_type_topic CONSTANT SMALLINT := 1;
         __community_type_journal CONSTANT SMALLINT := 2;
         __community_type_council CONSTANT SMALLINT := 3;
-        __is_muted bool := FALSE;
+        __is_muted bool := TRUE;
         __community_id hivemind_app.hive_posts.community_id%TYPE;
 BEGIN
+
+        RAISE NOTICE 'Function parameters: _block_num: %, _community_support_start_block: %, _parent_permlink: %, _author_id: %, is_comment: %', _block_num, _community_support_start_block, _parent_permlink, _author_id, is_comment;
+
         IF _block_num < _community_support_start_block THEN
             __is_muted := FALSE;
             __community_id := NULL;
@@ -71,6 +74,8 @@ BEGIN
                         END IF;
                     END IF;
                 END IF;
+            ELSE
+                __is_muted := FALSE;
             END IF;
         END IF;
 
@@ -173,8 +178,8 @@ ELSE
           FROM hivemind_app.prepare_tags( ARRAY_APPEND(_metadata_tags, _parent_permlink ) )
         ) as tags_ids
   FROM hivemind_app.hive_accounts ha,
-       hivemind_app.process_community_post(_block_num, _community_support_start_block, _parent_permlink, author_id, FALSE) pcp,
-        hivemind_app.hive_permlink_data hpd
+       hivemind_app.process_community_post(_block_num, _community_support_start_block, _parent_permlink, ha.id, FALSE) pcp,
+       hivemind_app.hive_permlink_data hpd
   WHERE ha.name = _author and hpd.permlink = _permlink
 
   ON CONFLICT ON CONSTRAINT hive_posts_ux1 DO UPDATE SET