db migration 1.0.2, now stores and indexes date of content delivered to subscriber...

[websub-hub] / src / db / postgres / sql / schema / 1.0.2 / apply.sql

diff --git a/src/db/postgres/sql/schema/1.0.2/apply.sql b/src/db/postgres/sql/schema/1.0.2/apply.sql
new file mode 100644 (file)
index 0000000..6da0924
--- /dev/null
+++ b/src/db/postgres/sql/schema/1.0.2/apply.sql
@@ -0,0 +1,28 @@
+BEGIN;
+       -- track when content was delivered as separate from latest content delivered
+       -- content_delivered continues to be the time the content was delivered, but becomes only informational
+       -- latest_content_delivered is date on topic content delivered
+       ALTER TABLE subscription
+               ADD COLUMN latest_content_delivered TIMESTAMP WITH TIME ZONE NOT NULL DEFAULT '-infinity'::timestamptz
+       ;
+       CREATE INDEX subscription_latest_content_delivered_idx ON subscription(latest_content_delivered);
+       -- migrate existing values
+       UPDATE subscription SET latest_content_delivered = content_delivered;
+       -- no need for this index
+       DROP INDEX subscription_content_delivered_idx;
+       -- update the view to use latest_cotnent_delivered
+       CREATE OR REPLACE VIEW subscription_delivery_needed AS
+               SELECT s.*
+               FROM subscription s JOIN topic t ON s.topic_id = t.id
+               WHERE
+                       s.expires > now()
+               AND
+                       s.latest_content_delivered < t.content_updated
+               AND
+                       s.delivery_next_attempt < now()
+               AND
+                       s.id NOT IN (SELECT id FROM subscription_delivery_in_progress_active)
+       ;
+
+       INSERT INTO _meta_schema_version (major, minor, patch) VALUES (1, 0, 2);
+COMMIT;