There are instructions in the manual how to retrieve all information with psql: 12.10. psql Support Information about text search configuration objects can be obtained in psql using a set of commands: \dF{d,p,t}[+] [PATTERN] In particular: List text search dictionaries (add + for more detail). => \dFd There is more, read the manual. Ultimately, possible … Read more
You need to install the package postgresql-contrib-9.1 in your system first. (Adapt to your version number! Here is the currently available list of packages.) That’s the case under Debian, Ubuntu & friends anyway. Using a system user with the necessary privileges: apt-get install postgresql-contrib-9.1 If your currently logged in user does not have the necessary … Read more
explainshell helpfully explains your command, and gives an excerpt from man grep: -w, –word-regexp Select only those lines containing matches that form whole words. So just remove -w since that explicitly does what you don’t want: grep -rn ‘/path/to/somewhere/’ -e “pattern”
Good question, and the answer is a lot more nuanced than one might expect. You can use indices for several different purposes. Indices for Relations The easiest and most familiar layout clones what you would expect from a relational database. You can (very roughly) think of an index like a database. MySQL => Databases => … Read more
Define “better”… sql full text search is fairly trivial to get working (indexing and query) – but it has penalties: very little (virtually no) control over how things are indexed (what the index keys are; what the lexers/stemmers/etc are; etc) runs on the sql server – which is usually your least scalable infrastructure Elastic search … Read more
Wow I just wrote a big post and SO choked and hung on it, and when I hit my back button to resubmit, the markup editor was empty. aaargh. So here I go again… Regarding Stack Overflow, it turns out that they use SQL server 2005 full text search. Regarding the OS projects recommended by … Read more
I found the answer to this today when converting my own database from SQL 2005 to SQL 2008. Pass “” for your search term and change the @search_term = ” test to be @search_term = ‘””‘ SQL server will ignore the double quotes and not throw an error. For example, the following would actually returns … Read more
SQL Server FTS is going to be easier to manage for a small deployment. Since FTS is integrated with the DB, the RDBMS handles updating the index automatically. The con here is that you don’t have an obvious scaling solution short of replicating DB’s. So if you don’t need to scale, SQL Server FTS is … Read more
I’ve found a solution to my problem. The query should be: select * from Customers where contains(*, ‘”ann*”‘) The quotes are the important part.
You can add full text to an existing instance by changing the SQL Server program in Programs and Features. Follow the steps below. You might need the original disk or ISO for the installation to complete. (Per HotN’s comment: If you have SQL Server Express, make sure it is SQL Server Express With Advanced Services.) … Read more