| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Oleg Bartunov" <oleg(at)sai(dot)msu(dot)su> |
| Subject: | Re: fulltext parser strange behave |
| Date: | 2007-11-07 23:11:00 |
| Message-ID: | 11425.1194477060@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
"Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> writes:
> I am writing tsearch2 wrapper and I testing functionality. I found
> some little bit strange on default parser. It can't parse tags with
> numbers:
Well, the state machine definitely thinks that tag names should contain
only ASCII letters (with possibly a leading or trailing '/'). Given the
HTML examples I suppose we should allow non-first digits too. Is there
anything else that should be considered a tag? What about dash and
underscore for instance?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-11-07 23:14:08 | Re: Estimation problem with a LIKE clause containing a / |
| Previous Message | Gevik Babakhani | 2007-11-07 22:54:07 | Throw error and ErrorContext question. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-11-07 23:38:33 | Re: fulltext parser strange behave |
| Previous Message | Pavel Stehule | 2007-11-07 07:19:33 | tsearch2api .. wrapper for integrated fultext |