alexreisner/geocoder — Issue #195: 4ecdf401 breaks situations where lat/long fields are product of joins
Author: rfb
Created: 2012-03-06 22:39:06+00:00
State: open

Prior to 1.1.1, I have been able to setup the reverse geocoder to use lat/long columns which are the product of a join. Now I get an knarly SQL errors about missing columns.

Example:

```
reverse_geocoded_by "locations.latitude", "locations.longitude"
```
4ecdf401 seems to have added #{table_name} before the column selection in the queries. Maybe geocoder_options could attach the table name to the columns if it does not already contain a table reference ('table.column')?