Teodor Sigaev wrote: > >Well, I noticed that the docs talk about an operator that can be used in > >SQL (outside the tsquery parser), as well as an operator that can be > Just to join 2 tsquery with operator FOLLOWED BY
Ok. > >used inside tsquery. Inside tsquery anything would be usable, but > >outside that it would be good to keep in mind the rest of SQL operators; > >and <> means "different from", so using it for FOLLOWED BY seems odd to > >me. > previous rule was: duplicate operation character to join tsqueries. > Ellipsis is forbidden to use as operator name: > # create operator ... (procedure = 'int2and'); > ERROR: syntax error at or near ".." > LINE 1: create operator ... (procedure = 'int2and'); > What is your suggestion for joining operator name? Silly me ... The dot is not allowed in operator names :-( Sorry. If there was a character that was very similar to dots I would suggest that. The closest is * I think, so what do you think of "***"? > >My suggestion of ... (ellipsis) is because that's already known as > >related to text, used for omissions of words, where the surrounding > >words form a phrase. It seems much more natural to me. > Yes, agree for omission. But for reason above its'n a good name although I > don't have a strong objections. > > may be <=>? it isn't used anywhere yet. > > select 'fat'::tsquery <=> 'cat'; > select 'fat <=> cat'::tsquery; > select 'fat <3> cat'::tsqyery; -- for non-default distance. Dunno. That looks pretty "relationalish". -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
