diff db/pubsub.sql @ 403:1dc606612405

implemented experimental "consistent_publisher" option: /!\ pgsql schema needs to be updated /!\ New "consistent_publisher" option has been implemented to allow node owners + admins to modify an item while preserving the original publisher. This way, original publisher can still edit the item. In addition to `consistent_publisher`, `max_items` has been added to PGQSL schema to prepare for future implementation.
author Goffi <goffi@goffi.org>
date Wed, 12 Jun 2019 21:51:50 +0200
parents a772f7dac930
line wrap: on
line diff
--- a/db/pubsub.sql	Thu May 23 08:58:29 2019 +0200
+++ b/db/pubsub.sql	Wed Jun 12 21:51:50 2019 +0200
@@ -13,7 +13,10 @@
         CHECK (access_model IN ('open', 'presence', 'publisher-roster', 'whitelist', 'publish-only', 'self-publisher')),
     persist_items boolean,
     deliver_payloads boolean NOT NULL DEFAULT TRUE,
+    max_items integer NOT NULL DEFAULT 0
+		CHECK (max_items >= 0),
     serial_ids boolean NOT NULL DEFAULT FALSE,
+    consistent_publisher boolean NOT NULL DEFAULT FALSE,
     send_last_published_item text NOT NULL DEFAULT 'on_sub'
         CHECK (send_last_published_item IN ('never', 'on_sub')),
     publish_model text NOT NULL DEFAULT 'publishers'
@@ -102,4 +105,4 @@
 	value text
-INSERT INTO metadata VALUES ('version', '4');
+INSERT INTO metadata VALUES ('version', '5');