Was ignoring non-ASCII characters. Thanks to github.com/supergivi for
reporting the bug.

...for Result instance methods mistakenly called on an array.

After further consideration, multiple results should be the default
behavior for this method. Some services only return one result (eg: any
IP-based service) but a great feature of advanced services like Yahoo
and Google is that they return an array of choices when doing a vague
search like "100 Main St" with no city, region, or country specified.

This allows us to add a method for expiring cache keys and generally
gives us more control over the cache interface.

More than one result is very rare and it's not clear how one would
evaluate the choices. If this is required in the future a new method
can be added.

Add Geocoder::Orm::Base module.

Also move 'address' and 'coordinates' methods from Geocoder::Lookup::Base
to Geocoder. This simplifies the interface and allows us to choose a
lookup engine dynamically for other types of geocoding (eg: IP addresses).

Prepare to add support for Yahoo in addition to Google.

Add implementation for Google and anticipate addition of Yahoo (supply
config option).

Wrong number of arguments for reverse geocode search.

This allows the same model to be forward and reverse geocoded and still
provide a geocodable address though a non-attribute method. Also raise
an exception if sufficient configuration is not provided.

Move relevant methods into it.

Be more descriptive.

Move all network/lookup-related methods into it.

Move some methods into it (organize!).

This fixes an incompatibility with the will_paginate gem.

This fixes SQLite near methods and speeds up MySQL and Postgres.

Add a GROUP BY clause which yields correct SQL. (Incorrect query is
accepted by MySQL and SQLite but not PostgreSQL.)