Mercurial > libervia-pubsub
view db/sat_pubsub_update_2_3.sql @ 457:7c9792f934a2
psql: use `created` colum to sort by creation:
`item_id` was used to sort by creation because it correspond to it and it's slighly more
efficient, but #398 raises the use case of manually modified database to import items.
The column has been changed to suit this use case, and `item_id` is now always added as
last order, in case of date conflicts.
This patch extends a contribution from Stephen Paul Weber (Singpolyma) from the ticket
mentioned below.
fix: 398
author | Goffi <goffi@goffi.org> |
---|---|
date | Thu, 30 Sep 2021 18:56:42 +0200 |
parents | 1dc606612405 |
children |
line wrap: on
line source
-- we check version of the database before doing anything -- and stop execution if not good \set ON_ERROR_STOP DO $$ DECLARE ver text; BEGIN SELECT value INTO ver FROM metadata WHERE key='version'; IF NOT FOUND OR ver!='2' THEN RAISE EXCEPTION 'This update file needs to be applied on database schema version 2, you use version %',ver; END IF; END$$; \unset ON_ERROR_STOP -- end of version check /* we add "presence" access model */ ALTER TABLE nodes DROP CONSTRAINT nodes_access_model_check; ALTER TABLE nodes ADD CHECK (access_model IN ('open', 'presence', 'publisher-roster', 'whitelist', 'publish-only', 'self-publisher')); /* and schema column */ ALTER TABLE nodes ADD COLUMN schema xml; /* we want xml types for items data too */ ALTER TABLE items ALTER data TYPE xml using data::xml; UPDATE metadata SET value='3' WHERE key='version';