Re: fulltext parser strange behave

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, 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-08 01:11:37
Message-ID: 12819.1194484297@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Tom Lane wrote:
>> 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?

> The docs say we specifically accept HTML tags. Are we really just
> accepting anything that is a string of ASCII letters as the tag name?
> Then we should adjust the docs. <foo> and <foo1234> are not HTML tags.

I don't think I want to try to maintain a list of exactly which
identifiers are considered valid tag names ... and if I did, I wouldn't
put it into the parser. It would be a dictionary's job to tell valid
from invalid tag names, no?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-11-08 01:31:34 Re: Throw error and ErrorContext question.
Previous Message Radoslaw Zielinski 2007-11-08 00:48:12 Re: Beta2 crash / create type + tsearch2

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2007-11-08 02:01:57 Re: fulltext parser strange behave
Previous Message Andrew Dunstan 2007-11-07 23:38:33 Re: fulltext parser strange behave