Register looked-up adapters/accessors in their own right

DataAccessor and InstanceAdapter classes are looked up for derived types
by inspecting the type's ancestors and searching for registered adapters
up the chain.

When loading a large number of facets this causes the lookup to be
invoked many times with the same arguments. By registering the located
adapter or accessor with the derived type, this is avoided for all calls
but the first.
Test that adapters found by ancestor lookup are registered.
Added support for empty arrays in restrictions.

This allows your timid code to go from looking like this
  with(:my_field, some_values) if some_values.present?
to become confident code like this
  with(:my_field, some_values)
Remove append mode from STDOUT.reopen

This causes problems when used in conjunction with `zeus rake`

Is there a real need for it? If not, this makes it work. Thanks!
Test adapter/accessor memoization using state checks
Clearer method naming in adapter lookup
Search all ancestors in adapter lookup
Fix syntax error in README
Merge pull request #349 from vongruenigen/patch-1

Fix syntax error in README
Bump rails to 3.2.11
Bump rails 3.0.17 to 3.0.20
Bump rails 2.3.14 to 2.3.16
Update README: 2009 <-> 2013 [ci skip]
Bump rails 3.1.8 to 3.1.10
Do no test against ruby 1.9.2

Highly recommended to use 1.9.3
Merge pull request #338 from aaronjensen/patch-1

Remove append mode from STDOUT.reopen
Fix Sunspot Rails not using sunspot.yml log_level setting

Sunspot will now use the configuration class to obtain the log_level
setting. The configuration class will get the log_level from sunspot.yml
settings file. If it is not present, the configuration class will use
Rails' log level setting instead.

Fixed Rails server class spec of not associating the @config instance
with the @server instance.
Merge pull request #353 from lulalala/fix_log_level

Fix Sunspot Rails not using sunspot.yml log_level setting
Add bind_address option into README [ci skip]
Adds note to rake task informing user that it is destructive

The title of the task is a little misleading. The assumption could be
made that the task will just update the data via a reindex, when in fact
it drops the current indexes completely and starts over. This can be
very destuctive if you have a large data set which can takes weeks to
reconstruct.