Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f6NFWmf15268 for ; Mon, 23 Jul 2001 11:32:48 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 89760 for ; Mon, 23 Jul 2001 08:32:45 -0700 From: "Josh Berkus" Subject: Full-text Indexing and Primary Keys To: pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Mon, 23 Jul 2001 08:32:45 -0700 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_===89760====davinci.ethosmedia.com===_" X-Archive-Number: 200107/307 X-Sequence-Number: 4113 This is a multi-part MIME message --_===89760====davinci.ethosmedia.com===_ Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit 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 --_===89760====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===89760====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===89760====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===89760====davinci.ethosmedia.com===_--