Re: [HACKERS] FTS Configuration option

On 13.10.2016 11:54, Emre Hasegeli wrote: Maybe also better to use -> instead of AND? AND would has another behaviour. I could create the following configuration: => ALTER TEXT SEARCH CONFIGURATION multi_conf ALTER MAPPING FOR asciiword, asciihword, hword_asciipart, word, hword,

Re: [HACKERS] FTS Configuration option

> With such syntax we also don't need the TSL_FILTER flag for lexeme. At > the current time unaccent extension set this flag to pass a lexeme to > a next dictionary. This flag is used by the text-search parser. It > looks like a hard coded solution. User can't change this behaviour. Exactly. >

Re: [HACKERS] FTS Configuration option

Thank you for sharing your thoughts! 2016-10-12 15:08 GMT+03:00 Emre Hasegeli : > However then the stemmer doesn't do a good job on those words, because > the changed characters are important for the language. What I really > needed was something like this: > >> ALTER TEXT

Re: [HACKERS] FTS Configuration option

> => ALTER TEXT SEARCH CONFIGURATION multi_conf > ALTER MAPPING FOR asciiword, asciihword, hword_asciipart, > word, hword, hword_part > WITH german_ispell (JOIN), english_ispell, simple; I have something like this in my mind since I dealt with FTS for a Turkish real estate listing

[HACKERS] FTS Configuration option

Hello hackers, Sometimes there is a need to collect lexems from various dictionaries. For example, if we have a column with text in various languages. Let's say there is a new option JOIN. This option will allow to parser to append lexems from current dictionary and go to next dictionary to get

[HACKERS] FTS Configuration option

Hello hackers, Sometimes there is a need to collect lexems from various dictionaries. For example, if we have a column with text in various languages. Let's say there is a new option JOIN. This option will allow to the parser to append lexems from the current dictionary and go to the next