mnort9
mnort9
Any solution to this?
I don't see a way to do this, so I'm working on a PR. Here's a couple options for the `near` arguments: ``` Location.near([lat, lng], :effective_radius, default_radius: 25) Location.near([lat, lng],...
On second thought, the `radius_field` option would then require the second integer radius argument. So maybe the first `default_radius` option is better.
@alexreisner Sure. An example use case would be assigning leads to sales agents that have different geographic territories. Agents in rural areas might need a larger radius, so a dynamic...
@alexreisner I think in this case `:radius_column_default` is fine for the keyword argument. I agree that being explicit is important since there are multiple contexts of "default". Aside from this...
No. I thought about hard wiring it to toggle the lbs/ounces setting periodically to keep it awake. But that's definitely a hack and won't be reliable...
Awesome! Would love to be able to use this library.
> I think the more generic pattern would be joining the results of multiple questions. Even in a single data warehouse where you have multiple fact tables with different dimensions,...