An error occurred fetching the project authors.
  1. 23 Oct, 2006 1 commit
  2. 14 Sep, 2006 1 commit
  3. 25 Jul, 2006 1 commit
  4. 17 Apr, 2006 2 commits
    • bar@mysql.com's avatar
      Bug#18201: XML: ExtractValue works even if the xml · 8fb685c2
      bar@mysql.com authored
      fragment is not well-formed xml
      
      Problem:
      - ExtractValue silently returned NULL if a wrong XML value is passed.
      - In some cases "unexpected END-OF-INPUT" error was not detected, and
        a non-NULL result could be returned for a bad XML value.
      
      Fix:
      - Adding warning messages, to make user aware why NULL was returned.
      - Missing "unexpected END-OF-INPUT" error is reported now.
      8fb685c2
    • bar@mysql.com's avatar
      Bug#18170: XML: ExtractValue(): XPath expression can't use QNames (colon in names) · faee72a9
      bar@mysql.com authored
      Problem source:
      Qualified names (aka QName) didn't work as tag names and attribute names,
      because the parser lacked a real rule to scan QName, so it understood
      only non-qualified names without prefixes.
      
      Solution:
      New rule was added to check both "ident" and "ident:ident" sequences.
      faee72a9
  5. 11 Apr, 2006 1 commit
    • bar@mysql.com's avatar
      Bug#16233: XML: ExtractValue() fails with special characters · df2d425a
      bar@mysql.com authored
      ExtractValue didn't understand tag and attribute names
      consisting of "tricky" national letters (e.g. latin accenter letters).
      It happened because XPath lex parser recognized only basic
      latin letter a..z ad a part of an identifier.
      
      Fixed to recognize all letters by means of new "full ctype" which
      was added recently.
      df2d425a
  6. 07 Apr, 2006 2 commits
  7. 20 Mar, 2006 1 commit
    • bar@mysql.com's avatar
      Bug #18172 XML: Extractvalue() accepts mallformed · 2e7cf881
      bar@mysql.com authored
        XPath without a XPath syntax error
      item_xmlfunc.cc:
        Error message didn't happen because after
        a failing attempt to parse RelativeLocationPath,
        my_xpath_parse_AbsoluteLocationPath() returned success.
        Changeing logic a bit:
        - Try to parse EOF first, return success if true.
        - Then try to parse RelativeLocationPath(), return success if true.
        - Otherwise return failure.
      xml.result:
        Adding test case.
        Also, this change made it possible to generate 
        an error message earlier in the case of another
        bad XPATH syntax.
      xml.test:
        Adding test case.
      2e7cf881
  8. 15 Mar, 2006 1 commit
    • bar@mysql.com's avatar
      xml.result, xml.test: · e983bc74
      bar@mysql.com authored
        Adding test.
      item_xmlfunc.cc:
        Bug #18171 XML: ExtractValue: the XPath position() function crashes the server!
        Disallowing use of position() and last() without context.
      e983bc74
  9. 03 Mar, 2006 1 commit
    • bar@mysql.com's avatar
      Bug#16318: XML: extractvalue() incorrectly returns last() = 1 · f516d1f9
      bar@mysql.com authored
      xml.result, xml.test:
        Adding test case.
      item_xmlfunc.cc:
        - adding "size" member into MY_XPATH_FLT struct,
        to pass parent's context size when iterating
        in a predicate. Previously, temporaty context
        size was calculated instead, which is always 1.
        As a result, things like last() and count() 
        didn't work fine.
        - adding iteration into Item_func_xpath_elementbyindex:
        similar to Item_func_xpath_predicate.
        This is to make things like last() and count()
        work inside square brackets.
      f516d1f9
  10. 02 Mar, 2006 1 commit
  11. 01 Mar, 2006 2 commits
  12. 28 Feb, 2006 1 commit
    • bar@mysql.com's avatar
      Bug#16313 XML: extractvalue() ignores '!' in names · bcc72ad0
      bar@mysql.com authored
      xml.result, xml.test:
        Adding test case.
      item_xmlfunc.cc:
        Fixed that the "!" character written at the end was ignored.
      
        Now if we try to scan "!=", and if "!" is not
        followed by "=", we rollback lex scanner back 
        to "!" token, so the parser will start to check
        the next rule from the "!" character again.
      
        Previously parser started from the next character,
        which was EOF in the example in xml.test,
        which led to query being successfully parsed,
        instead of producing a syntax error.
      bcc72ad0
  13. 27 Feb, 2006 1 commit
    • bar@mysql.com's avatar
      xml.test: · 1f30b152
      bar@mysql.com authored
      xml.result:
        Adding test for Bug #16312 XML: extractvalue() crash if angle brackets,
        A fix for #16234 fixed this bug automatically.
      1f30b152
  14. 10 Feb, 2006 1 commit
    • bar@mysql.com's avatar
      Bug#16234 XML: Crash if ExtractValue() · f057c9b4
      bar@mysql.com authored
        Also fixes 16314: XML: extractvalue() crash if vertical bar
      xml.result, xml.test:
        Adding test case
      item_xmlfunc.cc:
        Using root element as a context node,
        instead of NULL, with relative paths.
      f057c9b4
  15. 21 Dec, 2005 1 commit
    • bar@mysql.com's avatar
      Adding XPath support: ExtractValue and UpdateXML functions. · 519f9d62
      bar@mysql.com authored
      libmysqld/Makefile.am:
      sql/Makefile.am:
        Adding new source files.
        Adding new file into build process.
      include/my_xml.h:
      strings/xml.c:
        Adding new XML parse flags to skip text normalization and 
        to use relative tag names. Adding enum for XML token types.
      sql/lex.h:
        Making parser aware of new SQL functions.
      sqll/item_create.h, sql/item_create.cc:
        Adding creators for ExtractValue and UpdateXML.
      sql/item.h:
        Adding new Item types: nodeset and nodeset comparator.
      sql/item_xmlfunc.h
      sql/item_xmlfunc.cc
        Adding new classes implementing XPath functions.
      mysql-test/t/xml.test, mysql-test/r/xml.result:
        New files: adding test case
      519f9d62