Received: from smtp013.mail.yahoo.com (smtp013.mail.yahoo.com [216.136.173.57]) by postgresql.org (8.11.3/8.11.1) with SMTP id f6NGSCf43749 for ; Mon, 23 Jul 2001 12:28:12 -0400 (EDT) (envelope-from chrup999@yahoo.com) Received: from proxy.compucom.com (HELO Z161842) (204.214.145.2) by smtp.mail.vip.sc5.yahoo.com with SMTP; 23 Jul 2001 16:28:11 -0000 X-Apparently-From: Message-ID: <008301c11394$75418400$5dd26383@corp.compucom.com> From: "Chris Ruprecht" To: "Josh Berkus" Cc: "p-sql" References: Subject: Re: Full-text Indexing and Primary Keys Date: Mon, 23 Jul 2001 11:28:08 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200107/315 X-Sequence-Number: 4123 Josh, Full Text Indexing It will allow you to store text into a database and find portions of this text again, based on a few words of the text in the record. Say, for example, you want to store the bible in a PostGres database. You will store these fields: 1. Book 2. Chapter 3. Verse 4. Verse text If you know your bible, you probably can find any passage by just going to book/chapter/verse directly. But if you're not, and you just want to find all verses, where "Nathan", "Solomon" and "mother" is mentioned, you need something which lets you do that - and fast. What you want is something which does: select verse_text from bible where verse_text contains 'Nathan & Solomon & mother'; or even: select verse_text from bible where verse_text contains 'Nath* & Solo* & moth*'; This would be similar to "find file on hard drive by content" - which, if not indexed, takes forever. Hope this makes the issue a little more clear. Best regards, Chris ----- Original Message ----- From: "Josh Berkus" To: Sent: Monday, July 23, 2001 10:32 AM Subject: [SQL] Full-text Indexing and Primary Keys > Folks, > > 1. Can anyone explain to me what "full-text indexing" is, and why we do > or don't need it for Postgres? The marketing types keep asking me about > it ("buzzword o' the day") and I don't have an answer for them. > > 2. I propose that future versions of PostgreSQL require a primary key at > table creation. Frankly, I'm a little mystified as to why this was not > done already, but it's not too late to correct ... > > -Josh > > > > ______AGLIO DATABASE SOLUTIONS___________________________ > Josh Berkus > Complete information technology josh@agliodbs.com > and data management solutions (415) 565-7293 > for law firms, small businesses fax 621-2533 > and non-profit organizations. San Francisco > ---------------------------------------------------------------------------- ---- > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/users-lounge/docs/faq.html > _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com