6867 2009-05-06 15:48:09 +0000 [FT] TestSuite 2009-06-09 14:09:57 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Full Text 1.0 Candidate Recommendation All All CLOSED FIXED P2 normal --- 1 christian.gruen jim.melton pcase public-qt-comments oldest_to_newest 25012 0 christian.gruen 2009-05-06 15:48:09 +0000 Hi again, here the results of my latest test runs - I think only a few others issues are left now.. [1] FTOrder-andand1.txt / FTOrder-andor1.txt ...missing [2] ftmatchoptions-q2.xq Stemming entry.. <aux-URI role="stemming-dictionary">english</aux-URI> ..should either be removed from the XQFTTSCatalog.xml entry, or plan planning ..should be added to the stemming file "english-stems.txt" [3] FTWindow-complexwords1.xq XQFTTS: empty result BaseX : <title>Ninja Coder</title> [4] FTContent-q2.xq No <results> element expected around <title> elements. [5] xquery-xpath-composability-queries-results-q8.xq [XPST0008] Undefined variable "$books". [6] score-queries-results-q6.xq Expecting parentheses before the weight option, as it was moved to another place in the specification. [7] ft-3.4.1-examples-q1.xq [FTST0009] expected as optional error. [8] ForScoreExpr-2.xq, ForScoreExpr-4.xq Invalid cast from element to string. [9] FTSelection-Weight-q1f - q1h.xq Invalid cast from integer to double. [10] FTIgnore-q2.xq [FTST0007] expected as optional error. Best, Christian 25098 1 pcase 2009-05-10 20:27:38 +0000 Hi Christian, [2] ftmatchoptions-q2.xq Stemming entry.. <aux-URI role="stemming-dictionary">english</aux-URI> ..should either be removed from the XQFTTSCatalog.xml entry, or plan planning ..should be added to the stemming file "english-stems.txt" --Done. [5] xquery-xpath-composability-queries-results-q8.xq [XPST0008] Undefined variable "$books". --Corrected the initial variable to $books. [6] score-queries-results-q6.xq Expecting parentheses before the weight option, as it was moved to another place in the specification. --I am not convinced that parens are needed. Maybe the Task Force can discuss. [7] ft-3.4.1-examples-q1.xq [FTST0009] expected as optional error. --Done. 25106 2 christian.gruen 2009-05-11 20:57:10 +0000 Thank you Pat! A small addition to [6]: as far as I know, the following query... 'a' ftcontains 'a' ordered weight 0.8 will return a parsing error whereas ('a' ftcontains 'a' ordered) weight 0.8 will be correctly parsed. I'm relying on my parser, but I will try to reproduce the behaviour by the grammar rules.. [144] FTSelection ::= FTOr FTPosFilter* ... FTOr -> FTPrimaryWithOptions ... [150] FTPrimaryWithOptions ::= FTPrimary FTMatchOptions? FTWeight? [151] FTPrimary ::= (FTWords FTTimes?) | ("(" FTSelection ")") | FTExtensionSelection In 144, Position filters (here: ordered) are specified after the FTOr expression (here: 'a'). This is why the parser will assume that the FTSelection is finished after the position filter without checking the "weight" token in 150. If parentheses are added, the FTSelection branch in rule 151 is applied, followed by the weight token in 150. Hope this helps; always feel free to ask for more, or to correct me. Christian 25137 3 pcase 2009-05-13 14:01:42 +0000 Christian, [6] score-queries-results-q6.xq Expecting parentheses before the weight option, as it was moved to another place in the specification. --Thanks for the explanation. --I have moved the closing paren from after to before the weight expression in both the test cases and use cases. Pat Case