Instead of using distinct alone, change to add the relevance of related
items when searching for tickets. In other words, when performing a full
text search for 'xyz', add the relevance of matched user, organization, and
thread objects.

As currently written, if a full text query is attempted in BOOLEAN mode and
the query cannot be compiled by MySQL, it causes an OrmException and a
crash. This patch adds a more straight-forward and comprehensive
grammer-based approach to checking for valid boolean syntax.

This time, use full-text for user and ticket lookup boxes, and drop the
full-table scans from the ticket basic search page. Auto promote searches to
wildcard searches when searching with the user-supplied input yields no
results.

The system would encode 'access -related' as 'access+-related' when changing
the sorting preference and would crash the query. This patch fixes the
search engine code to avoid a BOOLEAN MODE search when improper operators
are used in the query terms, and it fixes the sorting preference system to
properly decode the '+' to a space when rewriting the URL.

No. Seriously. Like from 11k seconds down to 0.3 for a full-text search on
several thousand tickets.

This patch automatically configures reindexing of the search table when the
table is dropped and recreated.

orm: Correctly label correlated query joins via sub-queries
orm: Fixup formatting of dates in queries
orm: Fixup mangling of parameter values with colons in sub-queries
misc: Fixup incorrect offset calculation in Misc::dbtime()
forms: search: Add ability to describe a field search
search: Fix crash searching by ticket due date
search: Fix wrong results if searching by a date field (unix epoch was not
    converted to MySQL date format)
search: Fix wrong results searching by date == or !=

* Fix search on boolean field

* Fix crash visiting tasks page while ticket adv search
* Fix search on custom fields
* Add search on ticket source
* Move more advanced fields to drop-down

* Fix crash in Ticket::getLastRespondent
* Fix crash is ORM if using a superclass of a relationship from cache. For
  instance, if the cache contains an ObjectThread instance, but a
  TicketThread instance is required in the relationship. In such a case, use
  the cached data, but change this class. This; however, violates the single
  nature of cache entries.
* Fix spurious events appearing after upgrade due to deleted tickets
* Ensure floating content in thread-body divs does not float past the bottom
* Provide an anchor to thread entries
* Show thread entries before events where both have the same timestamp
* Fix double events for collaborator additions
* Credit email sender with collaborator addition
* Fix incorrect rendering of collaborator addition event
* Fix crash on new ticket due to non-static function
* Fix missing sort on sub-query if explicitly declared in QuerySet
* Fix missing parentheses in SQL for ['field__eq' => QuerySet]
* Fix incorrect SQL on compileSelect for models with inherited $meta['table']
* Dynamically adjust relative time client side

* Reindexing did not properly flush the last batch of items to the search
  therefore reindexing would always miss the last few items.
* Creating a new html thread entry with inline images resulted in empty
  search content
* HTML tag stripping in HtmlThreadBody::getSearchable() would result in
  missing white space between some words, resulting in poor searchable
  content

Add ability to extend Form
Support the concept of form ID
Clear/hide field errors on blur

Which indicates permissions are not windowed by an object's department

Also, convert the user tickets template file to use ORM

This patch converts the central file and threading classes over to use the
ORM.

Detach conversation thread from ticket to make it more generic. Any object
can now have its own thread complete with entry type and attachments.

Lint test rulez!