pg_search builds ActiveRecord named scopes that take advantage of PostgreSQL's full text search
I'm wondering: is it possible to use pg_search_scope with a virtual field?
I.e. I have a model Rating which is related to both a User and a Book, and I'd like to perform a search of ratings given a keyword that might be in both User's fields and Book's fields. I can do that with multisearchable I believe, but that means I cannot concatenate with other Rating scopes I think
I.e. I have a model Rating which is related to both a User and a Book, and I'd like to perform a search of ratings given a keyword that might be in both User's fields and Book's fields. I can do that with multisearchable I believe, but that means I cannot concatenate with other Rating scopes I think
my feeling is that I need to add a redundant field in Rating which basically just denormalizes the keywords, but I'm not sure
@riffraff - The redundant field would probably work OK. It's going to depend a lot on the use case. The other way to do it would be something like
Rating.where(foo: 'bar').my_custom_scope.joins(:pg_search_document).merge(PgSearch.multisearch('my query')). This may be able to work because PgSearch.multisearch returns a scope of PgSearch::Document records.
Hope that helps, I know this is a several-months-late response. :-P
my where clause looks like this (for multisearch)
WHERE (((to_tsvector('simple', coalesce("pg_search_documents"."content"::text, ''))) @@ (to_tsquery('simple', ''' ' || 'tyng' || ' ''')))
OR ((coalesce("pg_search_documents"."content"::text, '')) % 'tyng')
OR ((to_tsvector('simple', pg_search_dmetaphone(coalesce("pg_search_documents"."content"::text, '')))) @@ (to_tsquery('simple', ''' ' || pg_search_dmetaphone('tyng') || ' '''))))) AS pg_search_ce9b9dd18c5c0023f2116f ON "pg_search_documents"."id" = pg_search_ce9b9dd18c5c0023f2116f.pg_search_id
should i create a single index when multiple search types are used?
two indexes?
create index test_text_index1 on pg_search_documents using gin(((to_tsvector('simple'::regconfig, coalesce(content, ''::text)))));
create index test_text_index2 on pg_search_documents using gin(((to_tsvector('simple'::regconfig, pg_search_dmetaphone(coalesce(content, ''::text))))));
?
For some reason the explain doesn't seem to be using the indexes, and the query runs pretty slow
maybe i just don't have enough rows? i guess i can test it on a bigger pg server on heroku too
it seems there are 3 pieces to the ranking
only 2 are tsvectors
sorry my postgres full text knowledge is pretty limited, so i just can't unwrap that where to indexes
Have you been following the advice at https://github.com/Casecommons/pg_search/wiki/Building-indexes
create index test_text_index4 on pg_search_documents using gist(coalesce(content, ''::text) gist_trgm_ops)
now its hitting indexes, all good
This message was deleted
Also, is it possible to weight the columns referenced in
#multisearchable the same way it's done in #pg_search_scope?
without needed addons
@frcake Have used
pg_search on Heroku for the last 4.5 years and am very happy with ease of configuration and performance I have been able to get.
The GitHub repo for pg_search has disappeared! I haven't been working with the company that hosts the repo for some years so I'm guessing there was some confusion and miscommunication. I'm working to see if I can get it restored. Until then, I'm using https://github.com/nertzy/pg_search as the new home for now.
I forgot to send an update: the gem's GitHub home has been restored to https://github.com/Casecommons/pg_search
Hi, question: I am using https://github.com/Casecommons/pg_search#searching-using-different-search-features for searching with Rails Admin. However, even though it works flawlessly in local, it doesn't seem to work on deploy. Any ideas? Should I look up something in my DB or my logs to see where to debug?