• Index: the item's index.
• Name: the item's name, or title. For enum values, it's prefixed with the enum's name.
  Corresponding database field: title.
• Type: the item's type, expressed in a specific, universal system.
  Corresponding Lucene's field: valuetype, but use the value of the Storage type column for queries on items type.
• Value: the item's value. For string values, it's displayed as is w/o quotes nor escaping.
  Corresponding database field: value. There is also a typedvalue field that can contain Lucene's Int32, Int64, Float, Double or String typed values.
• Hex Value: the item's hexadecimal value, only valid for integer types.
  There is no corresponding database field.
• Signed Value: the item's signed value, only valid for integer and double types. Useful when you found a unsigned number and want to get the corresponding signed value (uint -> int for example).
  There is no corresponding database field.
• Source lines(s): the source lines from which the item was extracted. Comments and characters such as TAB, CR are preserved.
  Corresponding database field: source.
• File path: the file path from which the item was extracted, terminated by the line index.
  Corresponding database field: filepath. There are also directory and filename fields. filename is useful to query for values in a given file.
• Score: Lucene's score value. Items are returned sorted by score.
• Guid formats: a utility columns that proposes all possible guid formats. Only valid for guid types.
  There is no corresponding database field
• Char type: the character encoding (narrow, wide, etc.). Only valid for char and string values.
  Corresponding database field: chartype.
• Storage type: the exact storage type in the database. Only used for specific queries.
  Corresponding database field: valuetype.
• Conditions: the list of preprocessor conditions for a given item. If a condition is surrounded with a REVERSE function, it means the reverse condition of what's surrounded was the condition.
  Corresponding database field: conditions. There may be multiple conditions fields for one item.

Some important points to note:

• If you search for a negative number (like error codes expressed using signed integers), you can surround the search with double quotes, for example searching for "-2147009290" is equivalent to searching for 0x80073CF6, 80073CF6 (or even 3CF6 in this specific case). If you don't surround negative numbers with double quotes, the system will search for signed and unsigned corresponding values.
• The full-text search uses items' name, value, hex value, guid formats, source lines, etc. so refine your search if you get back too many items.
• You can search for guid binary values using just a part of their full definition. For example, if you search for '79eac9c5', it will get you 3 guid entries
• Leading wild card search (*whatever) is allowed, but it may slow down the search significantly.

Here are some example or custom queries:

title:wm_user returns the WM_USER Windows message item, not all items that reference the WM_USER token.

title:wm_u* returns all items (Windows messages probably) whose name starts with WM_U*.

value:1024 AND title:wm_* returns all items (Windows messages probably) whose name starts with WM_U* and value is 1024. Note AND must be UPPERCASE for Lucene's to understand it as an AND operator.

value:"00000002-0000-0000-C000-000000000046" returns the IMalloc IID guid value.