Re-reading the documentation, and I have the answer. If adding a
tsvector column, then for per row selection, I should also add a second
column of type regconfig to specify the language
that rows contents are in.
Cheers,
Andy
Andrew wrote:
Apologies
if this question has been previously covered, but I was not
able to find something similar in any of the mailing list archives.
With full text search, if you need to support a table where the content
of individual tuples/rows may be in different languages with the
language of the content known, and the content of any individual row
does not contain a mixture of languages, what is the best way
to design for this?
Would you create a different GIN/GiST index of the tsvector for each
language? Or if using columns to store the tsvector, would you have a
different column per language, or the one column with the associated
trigger using the appropriate language when building the tsvector for
that row?
Are there better alternatives than what I have listed?
Thanks,
Andy
|
