Tom Lane wrote: > "Thomas H." <[EMAIL PROTECTED]> writes: > > i saw my mistake. i misinterpreted the examples to show the possibility > > to convert *any* text by using casting to tsvector as an alternative to > > using to_tsvector :) > > Yeah, the examples in section 12.1.2 are not actually good practice: > both sides of the match should usually get normalized before comparison, > and these examples don't do that. > > I'm not sure that putting in to_tsvector calls there would be an > improvement, though, since at that point we haven't introduced > to_tsvector. > > Thoughts anyone?
Yep, I saw that chicken and egg problem in the docs when I was reviewing it long ago. I never came up with a solution either. We would have to introduce configurations a lot earlier, but how would you explain them when you don't know what a tsvector is. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
