Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 29099 invoked from network); 27 Jul 2005 01:38:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 27 Jul 2005 01:38:44 -0000 Received: (qmail 1413 invoked by uid 500); 27 Jul 2005 01:38:43 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 1371 invoked by uid 500); 27 Jul 2005 01:38:42 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 1358 invoked by uid 99); 27 Jul 2005 01:38:42 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jul 2005 18:38:42 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of manish.khettry@gmail.com designates 64.233.184.199 as permitted sender) Received: from [64.233.184.199] (HELO wproxy.gmail.com) (64.233.184.199) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jul 2005 18:38:35 -0700 Received: by wproxy.gmail.com with SMTP id i17so55002wra for ; Tue, 26 Jul 2005 18:38:33 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GPI6EnHFh4KQlMCY4ZsXo4oLBKFE0xfxOxMMhTqmQ/IexJbTFp/xdl+3BiEXPZ7X6yWfo9bqRhNo2iHperYqlMhHLadEOTmRruTi94tGUbDOEa+uOlFR7K38X91vmpe62tSF/OfAPskioJjQMep3pPi8TGG3pU293REba7VnajI= Received: by 10.54.42.38 with SMTP id p38mr134742wrp; Tue, 26 Jul 2005 18:38:33 -0700 (PDT) Received: by 10.54.45.63 with HTTP; Tue, 26 Jul 2005 18:38:33 -0700 (PDT) Message-ID: Date: Tue, 26 Jul 2005 18:38:33 -0700 From: Manish Khettry Reply-To: Manish Khettry To: Derby Development Subject: Re: [jira] Commented: (DERBY-472) Full Text Indexing / Full Text Search In-Reply-To: <42E6C991.6050703@debrunners.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <2127757367.1122418458423.JavaMail.jira@ajax.apache.org> <42E6C516.50506@sbcglobal.net> <42E6C991.6050703@debrunners.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N > > 2) Would there be work in the optimizer to get it to recognize that > > there was an index that helped with the CONTAINS() function. Is this > > the sort of work needed for DERBY-455 creation of indexes on expression= s? >=20 > Possibly. >=20 > Dan. >=20 I would think that each secondary access method would have a set of functions that could be used to read from the index. Much like BTree has <, <=3D, =3D and others, a text index would have CONTAINS (maybe others). The optimizer would have to know that CONTAINS is one of the functions supported by the index and to consider the access path when considering query plans. Manish