Thinking Sphinx
pg_search
Thinking Sphinx | pg_search | |
---|---|---|
- | 8 | |
1,627 | 1,318 | |
- | 1.4% | |
6.4 | 5.8 | |
3 months ago | about 2 months ago | |
Ruby | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Thinking Sphinx
We haven't tracked posts mentioning Thinking Sphinx yet.
Tracking mentions began in Dec 2020.
pg_search
-
What Postgres Full Text Search Is Missing
Facets are possible in Postgres but it looks complex:
https://web.archive.org/web/20200815141031/https://roamanaly...
pg_search [0] not to be confused with the ruby gem of the same name [1]:
[0] - https://github.com/paradedb/paradedb/tree/dev/pg_search#over...
[1] - https://github.com/Casecommons/pg_search
-
The Ultimate Search for Rails - Episode 1
On the backend, we'll need a few tools. Apart from the classics (ActiveRecord scopes and the pg_search gem), you’ll see how the (yet officially unreleased but production-tested) all_futures gem, built by SR authors, will act as an ideal ephemeral object to temporarily store our filter params and host our search logic. Finally, we’ll use pagy for pagination duties.
-
Application Search Feature more that ActiveRecord;
You can take a look at pg_search if you’re using Postgres
-
How to build a search engine with Ruby on Rails
This was a really good read, thanks. I've got into the habit of jumping straight to PgSearch but could definitely apply this approach to some existing projects.
-
Instant search with Rails 6 and Hotwire
Cleaner, more performant database queries: Definitely don't just leave your query sitting in the controller! For production use cases, you'd want to consider an option like pg_search
-
Postgres Full-Text Search: A Search Engine in a Database
If you are using Rails with Postgres you can use pg_search gem to build the named scopes to take advantage of full text search.
https://github.com/Casecommons/pg_search
-
Tips for optimizing pg_search?
Hey guys. Looking to release an app for mobile that will be using a rails API. The app will heavily rely on search. I know the go-to is to use elasticsearch but wanted to see if there was enough user demand for the MVP before shelling out $50/mo for the heroku add on. In the mean time I've been using pg_search. From the eye test it's performing okay but will be adding a table that houses over 350K records. With this in mind I was wondering if you all had any tips for increasing the overall speed for search from the model and controller level. Also should note that I'm open to any other free search gems if they deem bette fit.
-
Rails Search Bar
There are two basic search configurations with pg_search, a Single Model search scope or a multi Model configuration. In my case I am only using the Single Model configuration, but you can read more about multi-search in the documentation.
What are some alternatives?
Elasticsearch Rails - Elasticsearch integrations for ActiveModel/Record and Ruby on Rails
ransack - Object-based searching.
elasticsearch-ruby - Ruby integrations for Elasticsearch
textacular - Textacular exposes full text search capabilities from PostgreSQL, and allows you to declare full text indexes. Textacular will extend ActiveRecord with named_scope methods making searching easy and fun!
Sunspot - Solr-powered search for Ruby objects
Searchkick - Intelligent search made easy
Rroonga - The Ruby bindings of Groonga.
zombodb - Making Postgres and Elasticsearch work together like it's 2023