Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 916741337B8B for ; Mon, 24 Jan 2011 05:38:10 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 89224-01 for ; Mon, 24 Jan 2011 09:38:03 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-wy0-f174.google.com (mail-wy0-f174.google.com [74.125.82.174]) by mail.postgresql.org (Postfix) with ESMTP id 11D121337B8D for ; Mon, 24 Jan 2011 05:38:02 -0400 (AST) Received: by wyb28 with SMTP id 28so3866234wyb.19 for ; Mon, 24 Jan 2011 01:38:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=1kJyDgjtGhykdzdT57ZWwFh6Bi9kP4aXlTPwCupk5cY=; b=gLnOWz6QmeC+qQ9D4jYo6IT/br0IKUMSzlLMDyc+BH/97xAyk2PCAIfqhxtnRL5Oq9 uQtGrBIfmjC7PqendIRz8sqfVC/DJZKoITxROCTq1A2/rE/wGuUagPsSCZ2liiAh84MX Awu7HlPsjkKuLrEWYweKZW4reRU8nBM7VG6Yc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=HGvncNSevAkExn/WXrIkG1aA62m88Cw8AmTStpFUtmmLNBRfWw8rk3RnoFrg7z//1l znt2zXZacIn7fWC9BhT9njjPcgp0DKmizv0K1tfKRjga2lsZlkz9CP74YMjYrY83sf4M Omlv+NbKUZiMZSOM12DaP2/L5atmj+EzD8gFc= MIME-Version: 1.0 Received: by 10.217.1.198 with SMTP id n48mr3349905wes.59.1295861882379; Mon, 24 Jan 2011 01:38:02 -0800 (PST) Received: by 10.217.5.8 with HTTP; Mon, 24 Jan 2011 01:38:02 -0800 (PST) Date: Mon, 24 Jan 2011 10:38:02 +0100 Message-ID: Subject: Postgres function for full text search From: - To: pgsql-sql@postgresql.org Content-Type: multipart/alternative; boundary=20cf301e2f4d2d5eae049a945bd9 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.588 tagged_above=-5 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, T_TO_NO_BRKTS_FREEMAIL=0.01 X-Spam-Level: X-Archive-Number: 201101/68 X-Sequence-Number: 35015 --20cf301e2f4d2d5eae049a945bd9 Content-Type: text/plain; charset=ISO-8859-1 Hello everyone. My question if any known one postgres function, for full text search that separates words with "| "? As plainto_tsquery separating words with "& ". For example text "word1 word2 word3 word4" and conversion rates for full text search postgres "word1 | word2 | word3 | word4" Or i must create an own function eg. on the java for normalize text for search. I guess there would not need to remove not allowed words from text to prevent sql injection...? Thanks and regards --20cf301e2f4d2d5eae049a945bd9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello everyone.
My question if any known one postgres function, for full= text search that separates words with "| "?
As plainto_tsquer= y separating words with "& ".

For example text "w= ord1 word2 word3 word4"
and conversion rates for full text search postgres "word1 | word2 | wo= rd3 | word4"

Or i must create an own function eg. on the java f= or normalize text for search.
I guess there would not need to remove not= allowed words from text to prevent sql injection...?

Thanks and regards
--20cf301e2f4d2d5eae049a945bd9--