-
Notifications
You must be signed in to change notification settings - Fork 221
/
create_shared_triggers.sql
340 lines (303 loc) · 12.3 KB
/
create_shared_triggers.sql
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
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
-- This Source Code Form is subject to the terms of the Mozilla Public
-- License, v. 2.0. If a copy of the MPL was not distributed with this
-- file, You can obtain one at http://mozilla.org/MPL/2.0/.
-- This file defines triggers shared between the main and Sync connections.
CREATE TEMP TRIGGER moz_places_afterinsert_trigger
AFTER INSERT ON moz_places FOR EACH ROW
BEGIN
INSERT OR IGNORE INTO moz_origins(prefix, host, rev_host, frecency)
VALUES(get_prefix(NEW.url), get_host_and_port(NEW.url), reverse_host(get_host_and_port(NEW.url)), NEW.frecency);
-- This is temporary.
UPDATE moz_places SET
origin_id = (SELECT id FROM moz_origins
WHERE prefix = get_prefix(NEW.url) AND
host = get_host_and_port(NEW.url) AND
rev_host = reverse_host(get_host_and_port(NEW.url)))
WHERE id = NEW.id;
END;
-- Note that while we create tombstones manually, we rely on this trigger to
-- delete any which might exist when a new record is written to moz_places.
CREATE TEMP TRIGGER moz_places_afterinsert_trigger_tombstone
AFTER INSERT ON moz_places
FOR EACH ROW
BEGIN
DELETE FROM moz_places_tombstones WHERE guid = NEW.guid;
END;
-- Triggers which update visit_count and last_visit_date based on historyvisits
-- table changes.
-- NOTE: the values "0, 4, 7, 8, 9" below are EXCLUDED_VISIT_TYPES, stolen
-- from desktop.
CREATE TEMP TRIGGER moz_historyvisits_afterinsert_trigger
AFTER INSERT ON moz_historyvisits FOR EACH ROW
BEGIN
UPDATE moz_places SET
visit_count_remote = visit_count_remote + (NEW.visit_type NOT IN (0, 4, 7, 8, 9) AND NOT(NEW.is_local)),
visit_count_local = visit_count_local + (NEW.visit_type NOT IN (0, 4, 7, 8, 9) AND NEW.is_local),
last_visit_date_local = MAX(last_visit_date_local,
CASE WHEN NEW.is_local THEN NEW.visit_date ELSE 0 END),
last_visit_date_remote = MAX(last_visit_date_remote,
CASE WHEN NEW.is_local THEN 0 ELSE NEW.visit_date END)
WHERE id = NEW.place_id;
END;
-- NOTE: the values "0, 4, 7, 8, 9" below are EXCLUDED_VISIT_TYPES, stolen
-- from desktop.
CREATE TEMP TRIGGER moz_historyvisits_afterdelete_trigger
AFTER DELETE ON moz_historyvisits FOR EACH ROW
BEGIN
UPDATE moz_places SET
visit_count_local = visit_count_local - (OLD.visit_type NOT IN (0, 4, 7, 8, 9) AND OLD.is_local),
visit_count_remote = visit_count_remote - (OLD.visit_type NOT IN (0, 4, 7, 8, 9) AND NOT(OLD.is_local)),
last_visit_date_local = IFNULL((SELECT visit_date FROM moz_historyvisits
WHERE place_id = OLD.place_id AND is_local
ORDER BY visit_date DESC LIMIT 1), 0),
last_visit_date_remote = IFNULL((SELECT visit_date FROM moz_historyvisits
WHERE place_id = OLD.place_id AND NOT(is_local)
ORDER BY visit_date DESC LIMIT 1), 0)
WHERE id = OLD.place_id;
END;
CREATE TEMP TRIGGER moz_bookmarks_foreign_count_afterdelete_trigger
AFTER DELETE ON moz_bookmarks FOR EACH ROW
BEGIN
UPDATE moz_places
SET foreign_count = foreign_count - 1
WHERE id = OLD.fk;
END;
-- Note that the desktop versions of the triggers below call a note_sync_change()
-- function in some/all cases, which we will probably end up needing when we
-- come to sync.
CREATE TEMP TRIGGER moz_bookmarks_afterinsert_trigger
AFTER INSERT ON moz_bookmarks FOR EACH ROW
BEGIN
UPDATE moz_places
SET foreign_count = foreign_count + 1
WHERE id = NEW.fk;
DELETE from moz_bookmarks_deleted WHERE guid = NEW.guid;
END;
CREATE TEMP TRIGGER moz_bookmarks_foreign_count_afterupdate_trigger
AFTER UPDATE OF fk, syncChangeCounter ON moz_bookmarks FOR EACH ROW
BEGIN
UPDATE moz_places
SET foreign_count = foreign_count + 1
WHERE OLD.fk <> NEW.fk AND id = NEW.fk;
UPDATE moz_places
SET foreign_count = foreign_count - 1
WHERE OLD.fk <> NEW.fk AND id = OLD.fk;
END;
-- The next several triggers are a workaround for the lack of FOR EACH STATEMENT
-- in Sqlite, (see bug 871908).
--
-- While doing inserts or deletes into moz_places, we accumulate the affected
-- origins into a temp table. Afterwards, we delete everything from the temp
-- table, causing the AFTER DELETE trigger to fire for it, which will then
-- update moz_origins and the origin frecency stats. As a consequence, we also
-- do this for updates to moz_places.frecency in order to make sure that changes
-- to origins are serialized.
--
-- Note this way we lose atomicity, crashing between the 2 queries may break the
-- tables' coherency. So it's better to run those DELETE queries in a single
-- transaction. Regardless, this is still better than hanging the browser for
-- several minutes on a fast machine.
-- Note: unlike the version of this trigger in desktop places, we don't bother with calling
-- store_last_inserted_id. Bug comments indicate that's only really needed because the hybrid
-- sync/async connection places prevents `last_insert_rowid` from working. This shouldn't be an
-- issue for us, and it's unclear how we'd implement `store_last_inserted_id` it while supporting
-- multiple connections to separate databases open simultaneously, which we'd like for testing
-- purposes. (To be clear, it's certainly possible to implement it if it turns out we need it, it
-- would just be very tricky).
CREATE TEMP TRIGGER moz_places_afterinsert_trigger_origins
AFTER INSERT ON moz_places FOR EACH ROW
BEGIN
INSERT OR IGNORE INTO moz_updateoriginsinsert_temp (place_id, prefix, host, rev_host, frecency)
VALUES (
NEW.id,
get_prefix(NEW.url),
get_host_and_port(NEW.url),
reverse_host(get_host_and_port(NEW.url)),
NEW.frecency
);
END;
-- This trigger corresponds to the previous trigger
-- (moz_places_afterinsert_trigger). It runs on deletes on
-- moz_updateoriginsinsert_temp -- logically, after inserts on moz_places.
CREATE TEMP TRIGGER moz_updateoriginsinsert_afterdelete_trigger
AFTER DELETE ON moz_updateoriginsinsert_temp FOR EACH ROW
BEGIN
-- Deduct the origin's current contribution to frecency stats
{decrease_frecency_stats};
INSERT INTO moz_origins (prefix, host, rev_host, frecency)
VALUES (
OLD.prefix,
OLD.host,
OLD.rev_host,
MAX(OLD.frecency, 0)
)
ON CONFLICT(prefix, host) DO UPDATE
SET frecency = frecency + OLD.frecency
WHERE OLD.frecency > 0;
-- Add the origin's new contribution to frecency stats
{increase_frecency_stats};
UPDATE moz_places SET origin_id = (
SELECT id FROM moz_origins
WHERE prefix = OLD.prefix
AND host = OLD.host
)
WHERE id = OLD.place_id;
END;
-- When a row is deleted from places, we insert info about the frecency
-- delta into moz_updateoriginsdelete_tmp
CREATE TEMP TRIGGER moz_places_afterdelete_trigger_origins
AFTER DELETE ON moz_places
FOR EACH ROW
BEGIN
INSERT INTO moz_updateoriginsdelete_temp (prefix, host, frecency_delta)
VALUES (
get_prefix(OLD.url),
get_host_and_port(OLD.url),
-MAX(OLD.frecency, 0)
)
ON CONFLICT(prefix, host) DO UPDATE
SET frecency_delta = frecency_delta - OLD.frecency
WHERE OLD.frecency > 0;
END;
-- This trigger corresponds to the previous trigger
-- (moz_places_afterdelete_trigger_origins). It runs on deletes on
-- moz_updateoriginsdelete_temp -- logically, after deletes on moz_places.
CREATE TEMP TRIGGER moz_updateoriginsdelete_afterdelete_trigger
AFTER DELETE ON moz_updateoriginsdelete_temp FOR EACH ROW
BEGIN
-- Deduct the origin's current contribution to frecency stats
{decrease_frecency_stats};
UPDATE moz_origins SET frecency = frecency + OLD.frecency_delta
WHERE prefix = OLD.prefix AND host = OLD.host;
DELETE FROM moz_origins
WHERE prefix = OLD.prefix
AND host = OLD.host
AND NOT EXISTS (
SELECT id FROM moz_places
WHERE origin_id = moz_origins.id
LIMIT 1
);
-- Add the origin's new contribution to frecency stats
{increase_frecency_stats};
END;
-- Note: desktop places also has a notion of "frecency decay", and it only runs this
-- `WHEN NOT is_frecency_decaying()`.
CREATE TEMP TRIGGER moz_places_afterupdate_frecency_trigger
AFTER UPDATE OF frecency ON moz_places FOR EACH ROW
BEGIN
INSERT INTO moz_updateoriginsupdate_temp (prefix, host, frecency_delta)
VALUES (
get_prefix(NEW.url),
get_host_and_port(NEW.url),
MAX(NEW.frecency, 0) - MAX(OLD.frecency, 0)
)
ON CONFLICT(prefix, host) DO UPDATE
SET frecency_delta = frecency_delta + EXCLUDED.frecency_delta;
END;
-- This trigger corresponds to the previous trigger
-- (moz_places_afterupdate_frecency_trigger). It runs on deletes on
-- moz_updateoriginsupdate_temp -- logically, after updates to places frecency.
CREATE TEMP TRIGGER moz_updateoriginsupdate_afterdelete_trigger
AFTER DELETE ON moz_updateoriginsupdate_temp FOR EACH ROW
BEGIN
-- Deduct the origin's current contribution to frecency stats
{decrease_frecency_stats};
UPDATE moz_origins
SET frecency = frecency + OLD.frecency_delta
WHERE prefix = OLD.prefix
AND host = OLD.host;
-- Add the origin's new contribution to frecency stats
{increase_frecency_stats};
END;
-- These triggers adjust the foreign count for synced bookmark URLs, so that
-- they won't be expired or automatically removed.
CREATE TEMP TRIGGER moz_bookmarks_synced_foreign_count_afterinsert_trigger
AFTER INSERT ON moz_bookmarks_synced
BEGIN
UPDATE moz_places SET
foreign_count = foreign_count + 1
WHERE id = NEW.placeId;
END;
CREATE TEMP TRIGGER moz_bookmarks_synced_foreign_count_afterupdate_trigger
AFTER UPDATE OF placeId ON moz_bookmarks_synced
BEGIN
UPDATE moz_places SET
foreign_count = foreign_count + 1
WHERE id = NEW.placeId;
UPDATE moz_places SET
foreign_count = foreign_count - 1
WHERE id = OLD.placeId;
END;
CREATE TEMP TRIGGER moz_bookmarks_synced_foreign_count_afterdelete_trigger
AFTER DELETE ON moz_bookmarks_synced
BEGIN
UPDATE moz_places SET
foreign_count = foreign_count - 1
WHERE id = OLD.placeId;
END;
-- These triggers adjust the foreign count for tagged URLs, and bump the
-- tag's last modified time when a URL is tagged or untagged. These are
-- split out from the main connection's tag triggers because we also want
-- this behavior when applying synced tags.
CREATE TEMP TRIGGER moz_tags_relations_afterinsert_trigger
AFTER INSERT ON moz_tags_relation
BEGIN
UPDATE moz_tags SET
lastModified = now()
WHERE id = NEW.tag_id;
-- Tagging a URL increased the foreign count so that it will not be
-- expired or otherwise automatically removed.
UPDATE moz_places SET
foreign_count = foreign_count + 1
WHERE id = NEW.place_id;
END;
CREATE TEMP TRIGGER moz_tags_relations_afterupdate_trigger
AFTER UPDATE ON moz_tags_relation
BEGIN
UPDATE moz_tags SET
lastModified = now()
WHERE id IN (OLD.tag_id, NEW.tag_id);
UPDATE moz_places SET
foreign_count = foreign_count + 1
WHERE id = NEW.place_id;
UPDATE moz_places SET
foreign_count = foreign_count - 1
WHERE id = OLD.place_id;
END;
CREATE TEMP TRIGGER moz_tags_relations_afterdelete_trigger
AFTER DELETE ON moz_tags_relation
BEGIN
UPDATE moz_tags SET
lastModified = now()
WHERE id = OLD.tag_id;
UPDATE moz_places SET
foreign_count = foreign_count - 1
WHERE id = OLD.place_id;
END;
-- These triggers adjust the foreign count for URLs with keywords, so that
-- they won't be expired or automatically removed.
CREATE TEMP TRIGGER moz_keywords_afterinsert_trigger
AFTER INSERT ON moz_keywords
BEGIN
UPDATE moz_places SET
foreign_count = foreign_count + 1
WHERE id = NEW.place_id;
END;
CREATE TEMP TRIGGER moz_keywords_afterupdate_trigger
AFTER UPDATE OF place_id ON moz_keywords
WHEN OLD.place_id <> NEW.place_id
BEGIN
UPDATE moz_places SET
foreign_count = foreign_count + 1
WHERE id = NEW.place_id;
UPDATE moz_places SET
foreign_count = foreign_count - 1
WHERE id = OLD.place_id;
END;
CREATE TEMP TRIGGER moz_keywords_afterdelete_trigger
AFTER DELETE ON moz_keywords
BEGIN
UPDATE moz_places SET
foreign_count = foreign_count - 1
WHERE id = OLD.place_id;
END;