| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Ben Tilly" <btilly(at)gmail(dot)com> |
| Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Oleg Bartunov" <oleg(at)sai(dot)msu(dot)su>, "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: tsearch filenames unlikes special symbols and numbers |
| Date: | 2007-09-04 00:03:26 |
| Message-ID: | 5404.1188864206@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
"Ben Tilly" <btilly(at)gmail(dot)com> writes:
> On 9/3/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> There seems fairly clear use-case for allowing A-Z a-z 0-9 and
>> underscore (while CVS head rejects 0-9 and underscore).
> The problem with allowing uppercase letters is that on some
> filesystems foo and Foo are the same file, and on others they are not.
> This may lead to obscure portability problems where code worked fine
> on Unix and then fails when the database is running on Windows.
Yeah, good point. So far it seems that a-z 0-9 and underscore cover the
real use-cases, so what say we just allow those for now? It's a lot
easier to loosen up later than tighten up ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2007-09-04 00:29:28 | Re: Code examples |
| Previous Message | Tom Lane | 2007-09-04 00:01:48 | Re: tsearch filenames unlikes special symbols and numbers |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ben Tilly | 2007-09-04 00:20:34 | Re: Hash index todo list item |
| Previous Message | Tom Lane | 2007-09-04 00:01:48 | Re: tsearch filenames unlikes special symbols and numbers |