I'm about to write a oprrest function for the @@ operator. Currently @@
handles multiple cases, like tsvector @@ tsquery, text @@ tsquery,
tsquery @@ tsvector etc. The text @@ text case is for instance handled
by calling to_tsvector and plainto_tsquery on the input arguments.
For a @@ restriction function, I need to have a tsquery and a tsvector,
so in the text @@ text situation I'd end up calling plainto_tsquery
during planning, which would consequently get called again during
execution. Also, I'd need a not-so-elegant if-elsif-elsif sequence at
the beginning of the function. Is this OK/unavoidable/easly avoided?
Cheers,
Jan
--
Jan Urbanski
GPG key ID: E583D7D2
ouden estin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
