Josh Berkus <[EMAIL PROTECTED]> writes:
> Here's something not to forget in this whole business: the present TSearch2
> implementation permits you to have a different tsvector configuration for 
> each *row*, not just each column.  That is, applications can be built with
> "per-cell" configs.

Certainly.  That's actually the easiest case to deal with, because you're
going to put the tsvector config identity into another column of the
table, and the trigger or index just references it there.  It hasn't
been part of the discussion because it's not a problem.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?


Reply via email to