# Acts\_as\_solr, table joins and geographic searches

**URL:** <https://www.ruby-forum.com/t/acts-as-solr-table-joins-and-geographic-searches/115476>\
**Category:** Rails\
**Created:** [September 25, 2007, 5:39pm UTC](https://www.ruby-forum.com/t/acts-as-solr-table-joins-and-geographic-searches/115476 "2007-09-25T17:39:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jshow](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jshow](https://www.ruby-forum.com/u/jshow)\
**Post date:** [September 25, 2007, 5:39pm UTC](https://www.ruby-forum.com/t/acts-as-solr-table-joins-and-geographic-searches/115476/1 "2007-09-25T17:39:58Z")

</div>

I’m currently evaluating an evolution of our search technology usage,  
and am hoping that the community may have some suggestions.

Solr (acts\_as\_solr) seems to capture most of our search requirements  
(query language, scalability, facets).

Unfortunately 2 key elements fall outside the capabilities of solr  
and am interested in how others would approach the solution.

1. geographic queries. Would prefer to have these queries happen in  
the database
2. relational (think scoped\_by) queries ala  
current\_user.blog\_posts.find\_recent

…both the above could be done post solr, but I shudder at the  
scalability of such solutions.

Perhaps the solution is to add such capabilities to solr itself?

[I may have talked (typed) myself into the eventual solution.]

Are there any giants out there who have come before me, with whom I  
may stand upon your shoulders?

cheers,  
Jodi