| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | 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-03 19:15:05 |
| Message-ID: | 24214.1188846905@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> On the other hand, this means the name has to be quoted if it would be
> quoted as an SQL identifier, right?
Something like that. I wasn't planning on rejecting uppercase letters,
though, which would be necessary if you wanted to be strict about
matching unquoted identifiers.
There seems fairly clear use-case for allowing A-Z a-z 0-9 and
underscore (while CVS head rejects 0-9 and underscore). There also seem
to be good arguments for disallowing / \ : on various platforms, which
leaves us with some other punctuation in question, as well as the whole
matter of non-ASCII characters. I'm not sure whether we want to touch
the idea of non-ASCII; comments?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-09-03 19:42:33 | Re: tsearch filenames unlikes special symbols and numbers |
| Previous Message | Alvaro Herrera | 2007-09-03 19:03:02 | Re: tsearch filenames unlikes special symbols and numbers |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-09-03 19:42:33 | Re: tsearch filenames unlikes special symbols and numbers |
| Previous Message | Stefan Kaltenbrunner | 2007-09-03 19:11:16 | Re: [HACKERS] \dF wrt text search |