forked from Kinto/kinto
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'prepare-3.2.2' into 3.2.X
- Loading branch information
Showing
14 changed files
with
210 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
9 changes: 9 additions & 0 deletions
9
kinto/core/storage/postgresql/migrations/migration_011_012.sql
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
-- Select all existing records and delete their tombstone if any. | ||
DELETE FROM deleted d | ||
USING records r | ||
WHERE d.id = r.id | ||
AND d.parent_id = r.parent_id | ||
AND d.collection_id = r.collection_id; | ||
|
||
-- Bump storage schema version. | ||
INSERT INTO metadata (name, value) VALUES ('storage_schema_version', '12'); |
71 changes: 71 additions & 0 deletions
71
kinto/core/storage/postgresql/migrations/migration_012_013.sql
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,71 @@ | ||
-- | ||
-- Triggers to set last_modified on INSERT/UPDATE | ||
-- | ||
DROP TRIGGER IF EXISTS tgr_records_last_modified ON records; | ||
DROP TRIGGER IF EXISTS tgr_deleted_last_modified ON deleted; | ||
|
||
CREATE OR REPLACE FUNCTION bump_timestamp() | ||
RETURNS trigger AS $$ | ||
DECLARE | ||
previous TIMESTAMP; | ||
current TIMESTAMP; | ||
|
||
BEGIN | ||
previous := NULL; | ||
SELECT last_modified INTO previous | ||
FROM timestamps | ||
WHERE parent_id = NEW.parent_id | ||
AND collection_id = NEW.collection_id; | ||
|
||
-- | ||
-- This bumps the current timestamp to 1 msec in the future if the previous | ||
-- timestamp is equal to the current one (or higher if was bumped already). | ||
-- | ||
-- If a bunch of requests from the same user on the same collection | ||
-- arrive in the same millisecond, the unicity constraint can raise | ||
-- an error (operation is cancelled). | ||
-- See https://github.com/mozilla-services/cliquet/issues/25 | ||
-- | ||
current := clock_timestamp(); | ||
IF previous IS NOT NULL AND previous >= current THEN | ||
current := previous + INTERVAL '1 milliseconds'; | ||
END IF; | ||
|
||
IF NEW.last_modified IS NULL OR | ||
(previous IS NOT NULL AND as_epoch(NEW.last_modified) = as_epoch(previous)) THEN | ||
-- If record does not carry last-modified, or if the one specified | ||
-- is equal to previous, assign it to current (i.e. bump it). | ||
NEW.last_modified := current; | ||
ELSE | ||
-- Use record last-modified as collection timestamp. | ||
IF previous IS NULL OR NEW.last_modified > previous THEN | ||
current := NEW.last_modified; | ||
END IF; | ||
END IF; | ||
|
||
-- | ||
-- Upsert current collection timestamp. | ||
-- | ||
WITH upsert AS ( | ||
UPDATE timestamps SET last_modified = current | ||
WHERE parent_id = NEW.parent_id AND collection_id = NEW.collection_id | ||
RETURNING * | ||
) | ||
INSERT INTO timestamps (parent_id, collection_id, last_modified) | ||
SELECT NEW.parent_id, NEW.collection_id, current | ||
WHERE NOT EXISTS (SELECT * FROM upsert); | ||
|
||
RETURN NEW; | ||
END; | ||
$$ LANGUAGE plpgsql; | ||
|
||
CREATE TRIGGER tgr_records_last_modified | ||
BEFORE INSERT OR UPDATE ON records | ||
FOR EACH ROW EXECUTE PROCEDURE bump_timestamp(); | ||
|
||
CREATE TRIGGER tgr_deleted_last_modified | ||
BEFORE INSERT OR UPDATE ON deleted | ||
FOR EACH ROW EXECUTE PROCEDURE bump_timestamp(); | ||
|
||
-- Bump storage schema version. | ||
INSERT INTO metadata (name, value) VALUES ('storage_schema_version', '13'); |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters