Re: [HACKERS] fulltext parser strange behave

2007-11-13 Thread Andrew Dunstan
Tom Lane wrote: Andrew Dunstan <[EMAIL PROTECTED]> writes: I've just been looking at the state machine in wparser_def.c. I think the processing for entities is also a few bob short in the pound. It recognises decimal numeric character references, but nor hexadecimal numeric character refe

Re: [HACKERS] fulltext parser strange behave

2007-11-09 Thread Tom Lane
Andrew Dunstan <[EMAIL PROTECTED]> writes: > I've just been looking at the state machine in wparser_def.c. I think > the processing for entities is also a few bob short in the pound. It > recognises decimal numeric character references, but nor hexadecimal > numeric character references. That's

Re: [HACKERS] fulltext parser strange behave

2007-11-08 Thread Andrew Dunstan
Andrew Dunstan wrote: Tom Lane wrote: Andrew Dunstan <[EMAIL PROTECTED]> 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 n

Re: [HACKERS] fulltext parser strange behave

2007-11-07 Thread Oleg Bartunov
On Wed, 7 Nov 2007, Tom Lane wrote: Andrew Dunstan <[EMAIL PROTECTED]> 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 digi

Re: [HACKERS] fulltext parser strange behave

2007-11-07 Thread Andrew Dunstan
Tom Lane wrote: Andrew Dunstan <[EMAIL PROTECTED]> 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

Re: [HACKERS] fulltext parser strange behave

2007-11-07 Thread Tom Lane
Andrew Dunstan <[EMAIL PROTECTED]> 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

Re: [HACKERS] fulltext parser strange behave

2007-11-07 Thread Andrew Dunstan
Tom Lane wrote: "Pavel Stehule" <[EMAIL PROTECTED]> 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 ASC

Re: [HACKERS] fulltext parser strange behave

2007-11-07 Thread Tom Lane
"Pavel Stehule" <[EMAIL PROTECTED]> 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 possibl

[HACKERS] fulltext parser strange behave

2007-11-06 Thread Pavel Stehule
Hello 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: test=# select * from parse('zluty kun se napil zlute vody'); tokid | token ---+--- 12 | < 3 | h1 12 | > 1 | zluty 12