Re: fulltext parser strange behave - Mailing list pgsql-hackers

From Oleg Bartunov
Subject Re: fulltext parser strange behave
Date
Msg-id Pine.LNX.4.64.0711080758320.31840@sn.sai.msu.ru
Whole thread Raw
In response to Re: fulltext parser strange behave  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, 7 Nov 2007, Tom Lane wrote:

> Andrew Dunstan <andrew@dunslane.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?

it'd be nice to know in dictionary the parser state, but I think it's
too much knowledge for dictionary and the only possibility is to 
let <foo1234> pass to dictionary. Currently we have three separate tokens.


>
>             regards, tom lane
>
    Regards,        Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Bug: --with-libxml does not take a location
Next
From: "Brendan Jurd"
Date:
Subject: Re: A small rant about coding style for backend functions