diff options
author | Bharat Mediratta <bharat@menalto.com> | 2009-08-08 14:30:21 -0700 |
---|---|---|
committer | Bharat Mediratta <bharat@menalto.com> | 2009-08-08 14:30:21 -0700 |
commit | 7863aa16f9304e3c457898f22bce035bf4fedfd8 (patch) | |
tree | d05aa44709fa2c75137892dc937339d9623be327 /modules/search | |
parent | e4eec71efa5f7b1902155a34f8655cebe523c358 (diff) |
Update tags module to notify modules when items related to a tag are
affected. Practically speaking this means that we'll reindex items
when tags are added or removed from them.
API change:
Remove item_related_updated_batch event.
Rationale:
While this is an efficient event, it requires module developers to
support two event APIs for staying up to date and increases the
likelihood that they'll forget one and have data corruption. Force
them all through the slower but more reliable pipe, for now. We
can always try to improve efficiency by using the batch_start and
batch_stop events.
Diffstat (limited to 'modules/search')
-rw-r--r-- | modules/search/helpers/search_event.php | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/modules/search/helpers/search_event.php b/modules/search/helpers/search_event.php index b65763af..836bbe15 100644 --- a/modules/search/helpers/search_event.php +++ b/modules/search/helpers/search_event.php @@ -35,9 +35,4 @@ class search_event_Core { static function item_related_update($item) { search::update($item); } - - static function item_related_update_batch($sql) { - $db = Database::instance(); - $db->query("UPDATE {search_records} SET `dirty` = 1 WHERE item_id IN ($sql)"); - } } |