ku.
I've taken a look at Texticle, and it's actually quite a direct and
simple layering of Rails on top of Postgres search.
Oren, how mature is the Websolr framework? I have looked at Websolr
before, and it's not even out of private beta yet, and Heroku's own
integration with
On Wed, Feb 10, 2010 at 9:41 AM, Oren Teich wrote:
> Because you don't have access to the DB directly, many of the built in
> search solutions aren't available on Heroku. Using built in FTS or things
> like tsearch will break taps for example, and are not supported. A few
> people have reports
On Tue, Feb 9, 2010 at 01:21, Mike wrote:
> I noticed that the documentation recommends using Solr for search:
> http://docs.heroku.com/full-text-search
>
> However, Postgres has a built-in full text search capability that is
> not discussed at all. I was wondering what the rationale is for the
>
Because you don't have access to the DB directly, many of the built in
search solutions aren't available on Heroku. Using built in FTS or things
like tsearch will break taps for example, and are not supported. A few
people have reports of getting them running, but it's not production
quality. If
I noticed that the documentation recommends using Solr for search:
http://docs.heroku.com/full-text-search
However, Postgres has a built-in full text search capability that is
not discussed at all. I was wondering what the rationale is for the
recommendation of Solr?
Would the performance offere
