-
Notifications
You must be signed in to change notification settings - Fork 3
/
06_create_tagged_materialized_view_posts_materialized_view.rb
50 lines (43 loc) · 1.68 KB
/
06_create_tagged_materialized_view_posts_materialized_view.rb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
# frozen_string_literal: true
class CreateTaggedMaterializedViewPostsMaterializedView < ActiveRecord::Migration[5.0]
def up
execute <<-SQL
CREATE OR REPLACE FUNCTION metka_refresh_tagged_materialized_view_posts_materialized_view() RETURNS trigger LANGUAGE plpgsql AS $$
BEGIN
IF TG_OP = 'INSERT' AND NEW.tags IS NOT NULL THEN
REFRESH MATERIALIZED VIEW CONCURRENTLY tagged_materialized_view_posts;
END IF;
IF TG_OP = 'UPDATE' AND OLD.tags IS DISTINCT FROM NEW.tags THEN
REFRESH MATERIALIZED VIEW CONCURRENTLY tagged_materialized_view_posts;
END IF;
IF TG_OP = 'DELETE' AND OLD.tags IS NOT NULL THEN
REFRESH MATERIALIZED VIEW CONCURRENTLY tagged_materialized_view_posts;
END IF;
RETURN NEW;
END $$;
DROP MATERIALIZED VIEW IF EXISTS tagged_materialized_view_posts;
CREATE MATERIALIZED VIEW tagged_materialized_view_posts AS
SELECT
tag_name,
COUNT ( * ) AS taggings_count
FROM (
SELECT UNNEST
( tags ) AS tag_name
FROM
materialized_view_posts
) subquery
GROUP BY
tag_name;
CREATE UNIQUE INDEX idx_materialized_view_posts_tag_name ON tagged_materialized_view_posts(tag_name);
CREATE TRIGGER metka_on_materialized_view_posts
AFTER UPDATE OR INSERT OR DELETE ON materialized_view_posts FOR EACH ROW
EXECUTE PROCEDURE metka_refresh_tagged_materialized_view_posts_materialized_view();
SQL
end
def down
execute <<-SQL
DROP TRIGGER IF EXISTS metka_on_materialized_view_posts ON materialized_view_posts;
DROP MATERIALIZED VIEW IF EXISTS tagged_materialized_view_posts;
SQL
end
end