Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of paul.joseph.davis@gmail.com
 designates 209.85.198.233 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=s5r8O3QTilJ/g2YKvD1MjIj3uI8sWPc1RU0OO4gsxrXheo1IfV0Tgvfj1isH39Kr1t
         iQv7+olLhVpW7UWEVYxtpIMz1WTreGlYJ3dZfgr7iK1rWSYMgKwKEKY3t3SXR2RUiIMR
         hNzVytR0/2D7knJo7jXGScyf/YZDs+IpINlVs=
MIME-Version: 1.0
In-Reply-To: <20090122165608.GA28398@uk.tiscali.com>
References: <20090122165608.GA28398@uk.tiscali.com>
Date: Thu, 22 Jan 2009 12:08:39 -0500
Message-ID: <e2111bbb0901220908v8c85b81n977a200c7a4018dd@mail.gmail.com>
Subject: Re: Newbie question: substring matching
From: Paul Davis <paul.joseph.davis@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

You'll never be able to have a wildcard on the front side of your
pattern with couchdb directly, and you'll only be able to have a wild
card on one end of the statement.

Something you could try:

emit(doc.field_to_search, value);
emit(string_reverse_function(doc.field_to_search), vaule);

Then you could do something like:

http://127.0.0.1:5984/db_name/_view/ddoc/using_like?startkey="foo"&endkey="foo\u9999"
http://127.0.0.1:5984/db_name/_view/ddoc/using_like?startkey="oof"&endkey="oof\u9999"

And then intersect the two sets client side. Other than that, I'd look
at integrating full text search.

HTH,
Paul Davis

On Thu, Jan 22, 2009 at 11:56 AM, Brian Candler <B.Candler@pobox.com> wrote:
> Suppose I have a view which indexes a single field. Using startkey and
> endkey, it's easy to find matches which start with a particular pattern.
>
> But I'm wondering how best to do substring matches (in SQL: LIKE '%foo%')
>
> I could:
>
> 1. Read the entire view, and filter it client-side (problem: large
>   data transfer)
>
> 2. Create another view which enumerates all possible suffixes (problem:
>   large index, O(N^2))
>
> somedata
> omedata
> medata
> edata
> data
> ata
> ta
> a
>
> 3. Create a temporary view for the exact search being done (problem: forces
>   a read through all documents in the database)
>
> Is there some other option I have overlooked, such as filtering the view
> server-side somehow?
>
> Thanks,
>
> Brian.
>