-
Overhaul the test suite to be independent of a Rails project
-
Added concept of database adapter. Ported mysql/postgresql conditional code to their own adapter.
-
Added SQL Server support. THANKS github.com/brennandunn for all the improvements in this release
-
documentation updates and updated to work with Geokit gem v1.5.0
-
IMPORTANT: in the Geokit gem, Geokit::Geocoders::timeout became Geokit::Geocoders::request_timeout for jruby compatibility.
The plugin sets this in config/initializers/geokit_config.rb. So if you’ve upgraded the gem to 1.5.0, you need to make the change manually from Geokit::Geocoders::timeout to Geokit::Geocoders::request_timeout in config/initializers/geokit_config.rb
-
Added support for hashes in :through. So you can do: acts_as_mappable :through => { :state => :country } (Thanks José Valim).
-
Support for multiple ip geocoders (Thanks dreamcat4)
-
Now checks if either :origin OR :bounds is passed, and proceeds with geokit query if this is true (Thanks Glenn Powell)
-
Raises a helpful error if someone uses through but the association does not exists or was not defined yet (Thanks José Valim)
-
Fixed :through usages so that the through model is only included in the query if there
is an :origin passed in (Only if it is a geokit search) (Thanks Glenn Powell)
-
Move library initialisation into lib/geokit-rails. init.rb uses lib/geokit-rails now (thanks Alban Peignier)
-
Handle the case where a user passes a hash to the :conditions Finder option (thanks Adam Greene)
-
Added ability to specify domain-specific API keys (Thanks Glenn Powell)
-
More powerful assosciations in the Rails Plugin:You can now specify a model as mappable “through” an associated model.
In other words, that associated model is the actual mappable model with “lat” and “lng” attributes, but this “through” model can still utilize all Geokit’s “find by distance” finders. Also Rails 2.3 compatibility (thanks github/glennpow)
-
Split Rails plugin from geocoder gem
-
updated for Rails 2.2.2
-
Further fix of distance calculation, this time in SQL. Now uses least() function, which is available in MySQL version 3.22.5+ and postgres versions 8.1+
-
fixed the “zero-distance” bug (calculating between two points that are the same)
-
fixed a small but with queries crossing meridian, and also fixed find(:closest)
-
Fixed Rails2/Edge compatability