Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id CAF579F9288 for ; Mon, 3 Sep 2007 16:03:16 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 94587-06 for ; Mon, 3 Sep 2007 16:03:07 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id E07609F975B for ; Mon, 3 Sep 2007 16:03:07 -0300 (ADT) Received: from perhan.alvh.no-ip.org (190-13-142-51.bk13-dsl.surnet.cl [190.13.142.51]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l83J34Ja015138; Mon, 3 Sep 2007 12:03:04 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 42E6B47C61; Mon, 3 Sep 2007 15:03:02 -0400 (CLT) Date: Mon, 3 Sep 2007 15:03:02 -0400 From: Alvaro Herrera To: Tom Lane Cc: Gregory Stark , Oleg Bartunov , Pavel Stehule , PostgreSQL Hackers Subject: Re: tsearch filenames unlikes special symbols and numbers Message-ID: <20070903190302.GD10282@alvh.no-ip.org> References: <162867790709021328i7771aa9jfe79268bccbf123d@mail.gmail.com> <18259.1188773171@sss.pgh.pa.us> <87y7foir7t.fsf@oxford.xeocode.com> <19257.1188777110@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <19257.1188777110@sss.pgh.pa.us> User-Agent: Mutt/1.5.16 (2007-06-11) X-Virus-Scanned: ClamAV 0.91.1/4133/Sun Sep 2 09:44:55 2007 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Mon, 03 Sep 2007 12:03:06 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/100 X-Sequence-Number: 107252 Tom Lane escribió: > Possibly we could allow '.' as long as we forbade /, but the other > trouble with allowing . is that it encourages people to try to specify > the filetype suffix (as indeed Oleg was doing). I'd prefer to keep the > suffixes out of the SQL object definitions, with an eye to possibly > someday migrating all the configuration data inside the database. > There's a reasonable argument for restricting the names used for these > things in the SQL definitions to be valid SQL identifiers, so that that > will work nicely... Well, if we were to use SQL identifiers, we couldn't forbade anything too much, seeing as almost anything can be used as an identifier, so long as it is properly quoted. But it seems to me like we could just pick an convenient subset which doesn't make any OS too angry about it (say, reject / \ . and :), and when we get to using actual SQL identifiers, we can enlarge the supported char set without creating any backwards-compatibility problem. On the other hand, this means the name has to be quoted if it would be quoted as an SQL identifier, right? -- Alvaro Herrera http://www.amazon.com/gp/registry/DXLWNGRJD34J "Nunca confiaré en un traidor. Ni siquiera si el traidor lo he creado yo" (Barón Vladimir Harkonnen)