4 ms·
This looks pretty good. Though many of the features are already baked into PostgreSQL's full-text search, out of the box this seems to add enough value to get m
by asnyder 13y ago
This looks pretty good. Though many of the features are already baked into PostgreSQL's full-text search, out of the box this seems to add enough value to get me interested. I'll definitely be checking this out further.
- akane 13y agoWe looked into PostgreSQL search for a bit, but didn't see a way to train search results from past conversions. Does anyone know if this is possible?
- sheraz 13y agoUpvoted, and I'll pile on. Wordnet [1] already has addons for Postgres. [1] - https://github.com/taotetek/wordnet-postgres https://github.com/taotetek/wordnet-postgres
- gojomo 13y agoCan you clarify... does this addon simply store the Wordnet data inside Postgres, or actually let the postgres full-text search do query-expansion-to-synonyms?
- sheraz 13y agoSure. There are functions in this package. This link is better, which explains how the functions will work. http://wnsqlbuilder.sourceforge.net/sql.html http://wnsqlbuilder.sourceforge.net/sql.html
- MitziMoto 13y agoI recently had to implement search on my product and found Postgres' full-text search to be fairly impressive. More than enough for what I needed. Implemented through the wonderful textacular gem: https://github.com/textacular/textacular https://github.com/textacular/textacular
- apoorvamehta 13y agoInteresting. I'll have to look into PostgreSQL's full text search. Does it support token filters similar to Elasticsearch?
- asnyder 13y agoTo a degree, and is also very customizeable. It breaks things out to the lexeme level, read http://www.postgresql.org/docs/9.2/interactive/textsearch-intro.html http://www.postgresql.org/docs/9.2/interactive/textsearch-in....