Manual:Log search table

The log_search table (added in ). Either or both log_search and  can be used for storing data about log events. log_search, being indexed, is used for filtering for live queries. RevisionDelete for example uses it to filter log events down to the revision ID (not just page). For example, if revisions 48 and 49 are deleted by log event 29, then there would be two rows created in log_search, with ls_field equal to '<tvar|3>rev_id</>' for both fields, <tvar|4>ls_value</> equal to 48 for the first field and 49 for the second field, and <tvar|5>ls_log_id</> equal to 29 for both fields. For offline use (e.g. slow analytics), <tvar|1>log_params</> is enough.

The functions used for storing data in log_search are usually <tvar|1></> and <tvar|2></>.

ls_field
The type of ID ('<tvar|1></>', '<tvar|2></>', '<tvar|3></>', '<tvar|4>target_author_id</>'; and according to <tvar|5></>, '<tvar|6></>' and '<tvar|7></>'.) Others can be added.

ls_value
The value of the ID (e.g. if <tvar|1>ls_field</> is '<tvar|2>rev_id</>', then <tvar|3>ls_value</> would contain the <tvar|4>rev_id</>).

ls_log_id
Key to <tvar|1>log_id</>

Schema summary
+---+--+--+-+-+---+ +---+--+--+-+-+---+ +---+--+--+-+-+---+
 * Field    | Type             | Null | Key | Default | Extra |
 * ls_field | varbinary(32)    | NO   | PRI | NULL    |       |
 * ls_value | varbinary(255)   | NO   | PRI | NULL    |       |
 * ls_log_id | int(10) unsigned | NO  | PRI | 0       |       |