Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 68F5E2E2E8E for ; Tue, 15 Jan 2008 22:06:46 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 15967-07 for ; Tue, 15 Jan 2008 22:06:31 -0400 (AST) Received: from smtp-vbr10.xs4all.nl (smtp-vbr10.xs4all.nl [194.109.24.30]) by postgresql.org (Postfix) with ESMTP id F334A2E01E5 for ; Tue, 15 Jan 2008 22:06:41 -0400 (AST) Received: from webmail.xs4all.nl (dovemail12.xs4all.nl [194.109.26.14]) by smtp-vbr10.xs4all.nl (8.13.8/8.13.8) with ESMTP id m0G26Nxv031844; Wed, 16 Jan 2008 03:06:28 +0100 (CET) (envelope-from er@xs4all.nl) Received: from 156.83.0.77 (SquirrelMail authenticated user er) by webmail.xs4all.nl with HTTP; Wed, 16 Jan 2008 03:06:37 +0100 (CET) Message-ID: <8935.156.83.0.77.1200449197.squirrel@webmail.xs4all.nl> Date: Wed, 16 Jan 2008 03:06:37 +0100 (CET) Subject: Re: Full Text Search examples patch From: "Erik" To: "Alvaro Herrera" Cc: "Tom Lane" , pgsql-docs@postgresql.org User-Agent: SquirrelMail/1.4.11 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by XS4ALL Virus Scanner X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/18 X-Sequence-Number: 4747 Alvaro Herrera wrote: > Erik wrote: >> Tom Lane wrote: >> > "Erik" writes: >> >> I changed all references to 'pgweb' to 'apod'. This >> apod >> >> table initially corresponds with the structure of the >> >> table in the dump file. (In the documentation, that >> >> table >> >> is subsequently changed by adding a tsvector column.) >> > >> > Huh? These are just examples, they are not supposed >> to >> > refer to any >> > specific real table, much less one that comes standard >> > with Postgres. >> >> I understand that, of course. I am suggesting it might >> be >> an improvement to offer the data to go with the >> examples. > > Hmm, wouldn't it be easier to provide the pgweb table? Maybe - I don't know what that pgweb data would be. There are really two issues: 1. Apply changes I suggested (and attached earlier) to the documentation text to make code examples use a single table instead of two different ones. I chose apod because I knew apod from tsearch2. In the patch there are also some confusing inconsistencies removed, for instance column 'textsearch_indexable_col' is in a later code example used as column 'textsearch'. 2. Whether or not to include some actual table data (be it apod or pgweb). This is less important as far as I am concerned. The first is more useful and easier to apply than the second. > Alvaro Herrera > http://www.CommandPrompt.com/ > PostgreSQL Replication, Consulting, Custom Development, > 24x7 support > > ---------------------------(end of > broadcast)--------------------------- > TIP 7: You can help support the PostgreSQL project by > donating at > > http://www.postgresql.org/about/donate > regards, Erik Rijkers